Re: [blink-dev] Intent to Ship: MathML columnspan/rowspan attributes on element

LGTM3 /Daniel On 2023-07-12 17:26, Yoav Weiss wrote: LGTM2 On Wed, Jul 12, 2023 at 5:21 PM Mike Taylor wrote: LGTM1 - seems like an obvious interop win. On 7/12/23 4:31 AM, Frédéric Wang wrote: Hello, This is actually an intent to ship (sorry for sending email

Re: [blink-dev] Intent to Ship: MathML columnspan/rowspan attributes on element

LGTM2 On Wed, Jul 12, 2023 at 5:21 PM Mike Taylor wrote: > LGTM1 - seems like an obvious interop win. > > On 7/12/23 4:31 AM, Frédéric Wang wrote: > > Hello, > > This is actually an intent to ship (sorry for sending email with the wrong > title). > > To summarize a bit conversations, columnspan/

Re: [blink-dev] Intent to Ship: MathML columnspan/rowspan attributes on element

LGTM1 - seems like an obvious interop win. On 7/12/23 4:31 AM, Frédéric Wang wrote: Hello, This is actually an intent to ship (sorry for sending email with the wrong title). To summarize a bit conversations, columnspan/rowspan was something that was requested by web developers and

[blink-dev] Intent to Ship: MathML columnspan/rowspan attributes on element

Hello, This is actually an intent to ship (sorry for sending email with the wrong title). To summarize a bit conversations, columnspan/rowspan was something that was requested by web developers and is used in existing documents. We cannot just say "use CSS instead" as they are no equ

Re: [blink-dev] Intent to Ship: MathML

Thanks. I'll upload a CL for that. BTW, MathML now has a base::Feature flag. On 24/10/2022 10:05, Yoav Weiss wrote: I think it makes sense to flip it on now, and turn it off if printing NG gets reverted. On Mon, Oct 24, 2022 at 9:14 AM Frédéric Wang wrote: Hello, Reading [1], I don'

Re: [blink-dev] Intent to Ship: MathML

I think it makes sense to flip it on now, and turn it off if printing NG gets reverted. On Mon, Oct 24, 2022 at 9:14 AM Frédéric Wang wrote: > Hello, > > Reading [1], I don't think any distinction between pure blink features or > UI/browser features for "feature freeze". I understand the only re

Re: [blink-dev] Intent to Ship: MathML

Hello, Reading [1], I don't think any distinction between pure blink features or UI/browser features for "feature freeze". I understand the only requirement is to have code complete, but probably turning on the flag after the branch point is fine. However [2] also mentions "Two weeks prior t

Re: [blink-dev] Intent to Ship: MathML

On Fri, Oct 14, 2022 at 12:26 AM Frédéric Wang wrote: > 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 > h

Re: [blink-dev] Intent to Ship: MathML

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 L

Re: [blink-dev] Intent to Ship: MathML

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

Re: [blink-dev] Intent to Ship: MathML

LGTM3 On 9/14/22 8:37 AM, Yoav Weiss wrote: LGTM2 with the above plan, assuming printing sticks. On Wednesday, September 14, 2022 at 5:36:11 PM UTC+2 Chris Harrelson wrote: Printing NG looks like it will ship in M108. LGTM1 to ship MathML in M109 (just in case there is an issue that

Re: [blink-dev] Intent to Ship: MathML

LGTM2 with the above plan, assuming printing sticks. On Wednesday, September 14, 2022 at 5:36:11 PM UTC+2 Chris Harrelson wrote: > Printing NG looks like it will ship in M108. > > LGTM1 to ship MathML in M109 (just in case there is an issue that causes > printing to be reverted). > > On Mon, Aug

Re: [blink-dev] Intent to Ship: MathML

Printing NG looks like it will ship in M108. LGTM1 to ship MathML in M109 (just in case there is an issue that causes printing to be reverted). On Mon, Aug 8, 2022 at 12:25 PM Daniel Herr wrote: > There are some new css properties included in MathML, correct? Then one > possibility for feature

Re: [blink-dev] Intent to Ship: MathML

There are some new css properties included in MathML, correct? Then one possibility for feature detection could be to provide developers the ability to use CSS @supports inside print media stylesheets to determine whether MathML is available in that context. @supports (display: math) { /* or o

Re: [blink-dev] Intent to Ship: MathML

I don't mean to diminish the importance of print -- I'm old enough that I *occasionally *print things out. However, the situation now is that neither display nor print of MathML works natively in Chromium. In turning on MathML display, 99.99% (or more?) people will be happy to have fast disp

Re: [blink-dev] Intent to Ship: MathML

Personally, I don't think it's a good idea to ship MathML with missing printing support at all. Users definitely expect printing mathematical documents (and saving them as PDFs!) to be working. Many websites use feature detection (something like `"MathMLElement" in window`) to check if MathML i

Re: [blink-dev] Intent to Ship: MathML

Just to follow-up on two points raised by Daniel: On 25/06/2022 14:09, Frédéric Wang wrote: You mentioned fuzzy testing. Do the fuzzing tools have support for mathml elements? If not, you should probably add a to-do item to teach them. MathML has been there for several years so I do expect

Re: [blink-dev] Intent to Ship: MathML

We discussed that option in the API Owner meeting and did not really like it. If there are no better alternatives, maybe it would be good enough but the typical people to encounter printing problems would probably not discover it. I hope it's possible to find something more obvious so we don't

Re: [blink-dev] Intent to Ship: MathML

Excited to see this moving forward. Happy to see this ship with printing caveats from Mike. For my part, even a console log message would suffice. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving em

Re: [blink-dev] Intent to Ship: MathML

I'm excited about shipping MathML. I don't think it's necessary for us to wait O(months) for printing to work correctly, but I do think it's critical for us to give users who try to print some way of understanding that the rendering failure is not their fault. It would be unfortunate if folks go

Re: [blink-dev] Intent to Ship: MathML

[snip] > More about compatibility: Do you have any idea (guess really) of how > much of existing MathML content will "work" with just MathML Core? Is > it 99%, 90%, 50%, 10%? In addition to what Fred said about counters investigation, I can add that the MathML Refresh group (that spent about 2 y

Re: [blink-dev] Intent to Ship: MathML

On 24/06/2022 11:14, Daniel Bratell wrote: I'm really happy to see this coming along! Awesome work by everyone involved! Thanks! You mentioned fuzzy testing. Do the fuzzing tools have support for mathml elements? If not, you should probably add a to-do item to teach them. MathML has be

Re: [blink-dev] Intent to Ship: MathML

I'm really happy to see this coming along! Awesome work by everyone involved! I do agree that a feature of this size doesn't need to have all quirks ironed out before initial shipping. I expect some people to miss printing so I hope the gap where it doesn't work won't be too big. You mention

Re: [blink-dev] Intent to Ship: MathML

Thanks Chris. I'm attaching a testcase for contenteditable MathML. Indeed, the formula is properly rendered. It can also be edited and this will likely lead to "invalid" MathML markup (e.g. fraction ending up with only one child) but Firefox and WebKit don't perform integrity check either. And

Re: [blink-dev] Intent to Ship: MathML

EditingNG has already shipped. Only table fragmentation and printing are still to ship, and hopefully they will both be done by the end of the year. On Thu, Jun 23, 2022 at 4:39 AM Frédéric Wang wrote: > Hi Morten, > > Thanks for raising this issue, I forgot to mention it. We experimented > this

Re: [blink-dev] Intent to Ship: MathML

Hi Morten, Thanks for raising this issue, I forgot to mention it. We experimented this in the past and IIRC we found issues with: - Printing: indeed printing pages with math is likely to happen! - Multicol: Wikipedia uses that for the "References" section at the bottom of articles and some pa

Re: [blink-dev] Intent to Ship: MathML

Exciting times! Since the layout implementation of MathML is pure NG (i.e. it has no legacy engine counterpart), you should be aware that this is somewhat uncharted territory. We *do* have mechanisms that kick in when we need to fall back to legacy layout (e.g. when printing, or when there are tab

Re: [blink-dev] Intent to Ship: MathML

This is very exciting! A couple of questions below. On Wed, Jun 22, 2022 at 2:48 PM Frédéric Wang wrote: > Contact emails fw...@chromium.org, rb...@chromium.org, bkard...@igalia.com > > Explainer > https://github.com/mathml-refresh/mathml-core/blob/master/docs/explainer.md > https://people.igali

Re: [blink-dev] Intent to Ship: MathML

Hello, My previous email was generated from the information of chromestatus.com ; I’d like to elaborate a bit more about the situation of MathML in Chromium. In 2019, we published a roadmap [1] which we basically implemented downstream the same year. As of today, we

[blink-dev] Intent to Ship: MathML

Contact emails fw...@chromium.org, rb...@chromium.org, bkard...@igalia.com Explainer https://github.com/mathml-refresh/mathml-core/blob/master/docs/explainer.md https://people.igalia.com/fwang/explainer-font-family-math Specification https://mathml-refresh.github.io/ma