On 14/10/2022 09:17, Manuel Rego Casasnovas wrote:
On 14/10/2022 07:53, Frédéric Wang wrote:
If I understand correctly [3], it is integrated in M108 (branched
yesterday) and the feature freeze for M109 will be October 27. So we
have two weeks to decide to enable MathML or not (if an issue with
LayoutNGPrinting is detected) [4].
I believe "feature freeze" on that page is related to Chromium itself,
things like UI features and browser features. But not related to Blink
features, they sometimes get shipped just before the branch point, and
after the feature freeze date.
Thanks for the clarification. As a minor note, as mentioned in the
original email there is a small UI change for selecting the preferred
math font (but it's not a big deal if this one is postponed after the
initial shipping of MathML):
On 22/06/2022 23:48, Frédéric Wang wrote:
Requires code in //chrome?
True (this is only to implement support for “font-family: math”, which
has a user preference menu for math font, see
https://docs.google.com/document/d/1bvY_Npe2zLW_705KXdmecsH6P9I9wBMpHRsZ9CxWNOI/edit#heading=h.u9hwm9tp8nuy).
So we have some extra time to check if LayoutNGPrinting gets some
trouble or not. And if it sticks we could enable MathML too (maybe
adding a base feature [*] in case it needs to be disabled later).
Yes, I was thinking about that too. I wonder what API owners think about
it... Should we introduce a chromium feature now in any case? (for
example that will be useful to enable the math font UI when MathML is
enabled, something we can't do right now with only a blink flag).
--
Frédéric Wang
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/70ee3d94-7f60-c8dd-ccaf-0968fe36295e%40igalia.com.
