You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[wimp] Support non-chrome browsers with wimp #187212
In order to work on non-chrome browsers, we need to create a wimp_heavy variant of wimp, similar to the skwasm_heavy variant. The heavy variant has two main differences:
Has ICU data built into the binary, and doesn't rely on Chrome's v8BreakIterator
Includes image decoding for some image types when we don't have access to web codecs.
We may want to take a look at the second one of those and see if that's necessary anymore. I think at least Firefox has added support for webcodecs, and Safari may have too. Hence, we might be able to leave out codec support in the binary and always assume that webcodecs are available.
From poking around, Intl.v8BreakIterator is deprecated for Intl.Segmenter which is supported on all major browsers. So once we migrate away from v8BreakIterator, we should be good there. Firefox supports ImageDecoder since 133 too. The only browser that doesn't support ImageDecoder is Safari. I think we can get a lot of support without relying on heavy.
From poking around, Intl.v8BreakIterator is deprecated for Intl.Segmenter which is supported on all major browsers. So once we migrate away from v8BreakIterator, we should be good there. Firefox supports ImageDecoder since 133 too. The only browser that doesn't support ImageDecoder is Safari. I think we can get a lot of support without relying on heavy.
There's a lot of context here, but essentially our line-breaking strategy revolves around v8BreakIterator specifically and Intl.Segmenter does not actually support line breaking. So there are no current plans for the web team to move off of v8BreakIterator, even though it is deprecated.
Activity
bivens-dev commentedon May 28, 2026
For reference: https://caniuse.com/webcodecs
yjbanov commentedon Jun 3, 2026
The WebCodecs part we're interested in is https://caniuse.com/?search=ImageDecoder. It looks like Firefox now supports image codecs. We should test it and add it to the allow list.
yjbanov commentedon Jun 3, 2026
Issue for image decoding: #122761
gaaclarke commentedon Jul 23, 2026
fyi chrome 151.0.7922.48 complains
Intl.v8BreakIterator is deprecated. Please use Intl.Segmenter instead.edit: filed issue -- #189938
gaaclarke commentedon Jul 23, 2026
From poking around,
Intl.v8BreakIteratoris deprecated forIntl.Segmenterwhich is supported on all major browsers. So once we migrate away from v8BreakIterator, we should be good there. Firefox supports ImageDecoder since 133 too. The only browser that doesn't support ImageDecoder is Safari. I think we can get a lot of support without relying on heavy.eyebrowsoffire commentedon Jul 23, 2026
There's a lot of context here, but essentially our line-breaking strategy revolves around v8BreakIterator specifically and Intl.Segmenter does not actually support line breaking. So there are no current plans for the web team to move off of v8BreakIterator, even though it is deprecated.
gaaclarke commentedon Jul 23, 2026
gaaclarke commentedon Jul 24, 2026
[wimp] fixes ubo padding size issue (flutter#189958)
Adds error about wimp_heavy not being implemented. (flutter#189945)
[wimp] Adds wimp-heavy variant for non-chrome browsers (flutter#189953)
[wimp] Adds wimp-heavy variant for non-chrome browsers (flutter#189953)