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
    causes printing to be reverted).

    On Mon, Aug 8, 2022 at 12:25 PM Daniel Herr
    <danielstephenh...@gmail.com> wrote:

        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.

        <link href="print.css" rel="stylesheet" media="print">
        @supports (display: math) { /* or other MathML property */
          /* not applied in Chromium */
        }

        <link href="screen.css" rel="stylesheet" media="screen">
        @supports (display: math) { /* or other MathML property */
          /* applied in Chromium and other browsers */
        }

        On Friday, July 8, 2022 at 2:54:36 PM UTC-4 Neil Soiffer wrote:

            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 display of math; some small number of people
            won’t be happy when they try to print it out.

            For that group and the publishers that put out material
            that tests whether MathML is available in the browser,
            this would be a regression. It would be interesting to
            know if any sites sniff for MathML support, or whether
            they simply look at the browser and decide based on their
            knowledge of support. I know of at least one site that
            does the latter and so they wouldn’t suffer a regression.
            Maybe all the sites do this because it is easy and
            reliable? Even if there is no regression, please don't put
            printing math on the back burner in terms of priorities.

            Benjamin mentioned Wikipedia. I can’t speak for what
            Wikipedia would do, but as long as they know that printing
            is broken in Chromium, any decision to turn on direct
            MathML rendering is their call, not Chromium’s. I suspect
            given their concern that Wikipedia renders properly almost
            everywhere, it will be a long time before they make a
            switch. Right now, despite Firefox’s long support for
            MathML, they still use SVG with hidden MathML on it.

            On the supposition that there are some sites that sniff
            for MathML, I think Benjamin’s suggestions are good. I
            don’t know how feasible it is to put up a dialog stating
            that printing math is not currently supported in Chromium,
            but doing that with some suggested workarounds would I
            think be a viable alternative until print is supported.
            One workaround would be to suggest they download an
            extension (that would need to be written) that loads
            MathJax into the page in question when clicked. Another
            suggestion could be to read the page with Firefox ;-). I’m
            sure there are many more clever people on this list than I
            am who might have other suggestions for workarounds.

            My suggestion is to follow the somewhat worn out but still
            very true trope: "don't let perfect be the enemy of the
            good". People have been waiting years and years to get
            math to display natively in Chromium and now it is ready
            to happen. Please try to find a simple stopgap and get
            this long awaited feature turned on.

--
        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 blink-dev+unsubscr...@chromium.org
        <mailto:blink-dev+unsubscr...@chromium.org>.

        To view this discussion on the web visit
        
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cc2a4fab-823d-467f-949e-385a150fa5fen%40chromium.org
        
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cc2a4fab-823d-467f-949e-385a150fa5fen%40chromium.org?utm_medium=email&utm_source=footer>.

--
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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/260d7448-c8cf-4503-99bb-8918bda112bbn%40chromium.org <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/260d7448-c8cf-4503-99bb-8918bda112bbn%40chromium.org?utm_medium=email&utm_source=footer>.

--
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 blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/62981a6c-c6f1-8b51-ff6a-f6be3c7e4774%40chromium.org.

Reply via email to