On Wed, Sep 28, 2022 at 3:38 PM David Bokan <[email protected]> wrote:
> Sure, I'll start on a PR. > > Taking another look, there does seem to be some basic parsing of the meta > in CSS Viewport <https://drafts.csswg.org/css-viewport/#viewport-meta>. > It's still a fairly early-stage spec but I wonder if it'd make more sense > to just add the `interactive-widgets` keyword there rather than bouncing it > between the two specs? I could also help flesh out the meta processing > model more generally there. > That parsing algorithm is something I wrote back in 2010 based on testing Safari on an iPod Touch, not looking at the WebKit source code. That part should just be ditched. On Wed, Sep 28, 2022 at 2:26 AM Philip Jägenstedt <[email protected]> > wrote: > >> On Tue, Sep 27, 2022 at 7:07 PM Chris Harrelson <[email protected]> >> wrote: >> >>> (API owner hat off for this intent, I'm one of the people working on >>> this feature change) >>> >>> On Tue, Sep 27, 2022 at 1:32 AM Philip Jägenstedt <[email protected]> >>> wrote: >>> >>>> I think this plan makes sense, but the lack of a spec makes it unusual. >>>> >>>> Can you say more about how this will eventually be spec'd, and who is >>>> signed up to push that work to completion? >>>> >>> >>> The feature will be documented in the Compat spec for now, and once >>> there is spec text for CSS viewport we'll add it there. The <meta> tag is >>> not specified at all at present.. >>> >> >> Ah yes, it was linked in the text. Will someone send a pull request for >> https://github.com/whatwg/compat? Normally we'd block shipping on the >> spec change being made, and since the Compat spec exists and it sounds like >> there's multi-vendor support, I think we can stick to that here too, right? >> >> Since Firefox Android would also need to change to get full interop, a >>>> stronger statement from Mozilla would be really helpful. Would they be >>>> happy to ship this if it turns out to be web compatible in Chrome? >>>> >>> >>> In a discussion with Emilio (cc'd) at TPAC, he informally agreed it's >>> probably fine to switch Firefox Android to match in a similar time frame. >>> >>> (Emilio, please let me know if I've misquoted in any way. :) ) >>> >> >> Sounds good! If we do a compat spec PR, support on that would do the >> trick. >> > -- > 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/CANMmsAuM-kW5PP9_%2BF-1y12gE0GK-3Z84YqopTasbUOX6n-ZQw%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANMmsAuM-kW5PP9_%2BF-1y12gE0GK-3Z84YqopTasbUOX6n-ZQw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- Rune Lillesveen -- 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/CACuPfeTWWW6BADfQRSOJkZ6vMju1bL_X6CEav4WdedZ23SYabQ%40mail.gmail.com.
