summaryrefslogtreecommitdiffstats
path: root/Source/WebCore/rendering/RenderReplaced.cpp
diff options
context:
space:
mode:
authorSteve Block <steveblock@google.com>2011-11-15 16:42:15 +0000
committerSteve Block <steveblock@google.com>2011-11-15 16:50:30 +0000
commit741b1c63ee296db8d359fc9f8a44eddfc8b94027 (patch)
tree3844fcf5093630b8b1b93494fb3a936ba9d535e7 /Source/WebCore/rendering/RenderReplaced.cpp
parent347e86423df46e97b374d2b61321e983486f4272 (diff)
downloadexternal_webkit-741b1c63ee296db8d359fc9f8a44eddfc8b94027.zip
external_webkit-741b1c63ee296db8d359fc9f8a44eddfc8b94027.tar.gz
external_webkit-741b1c63ee296db8d359fc9f8a44eddfc8b94027.tar.bz2
Fix Java Bridge when coercing JavaScript string to Java char in arrays
Currently, when converting coercing a JavaScript string to a method parameter of type Java char, we always use a value of 0. However, when coercing a JavaScript object to method parameter of type Java char array, we behave differently. In this case, if the element is a JavaScript string, we use the first character of the string for the char value. This change modifies the behaviour in the array case to match that in the non-array case. Bug: 5619677 Change-Id: Ifeee8940af0bb01df58eeff6c9dd7e1b40688790
Diffstat (limited to 'Source/WebCore/rendering/RenderReplaced.cpp')
0 files changed, 0 insertions, 0 deletions