Get rid of FrameMsg_PostMessage_Params.is_data_raw_string.
Instead use the helper method we already have to just convert a raw string to a serialized string value encoded byte array on the browser side. This gets rid of some special casing and possible confusion in this codepath. Does requre moving string_message_codec to some non-android specific location (even though this code is only really used on android), and for that blink/common seemed like a sensible place. Bug: none Change-Id: I4ebc70cb68a1c12ad57d3949a1ac606392f7c908 Reviewed-on: https://chromium-review.googlesource.com/1053169Reviewed-by:Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#557363}
Showing
Please register or sign in to comment