Finetuning string16 in mojo |
|||
Issue descriptionWe need to find a way to avoid calling memcpy() in mojo serialization of string16 on the Blink side. Or, should we avoid sending string16 from Blink to chromium? Currently, there are a number of instances using string16 on both sides.
,
Nov 2 2016
,
Nov 2 2016
Fwiw I think never sending String16 over mojo and always using utf8 would be reasonable too. All of those old IPCs should be updated. |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Nov 2 2016