3 ms·

Can someone explain this? Isn't Shadow DOM necessary? What is this 60fps on mobile intent and how it relates to Shadow DOM?

by Geee 13y ago

masklinn 13y ago
> Can someone explain this? They're finishing up the removal of unmaintained and essentially dead code which started after the Blink fork. > Isn't Shadow DOM necessary? To what? > What is this 60fps on mobile intent and how it relates to Shadow DOM? Shadow DOM requires hooks throughout the engine. If you remove the hooks (because nobody uses them because shadow dom is not supported) the engine is lighter and executes faster. Hence 60fps goal.
- why_me 13y ago
  > Hence 60fps goal. Is that for embedded video playback? Whatelse could it apply to? Any idea?
  - 0x0 13y ago
    Wild guess: Rendering live web pages (html+js+css, with animations and scrolling) at 60 frames per second.
    - danabramov 13y ago
      As stated in nearby comments, it's an in-joke. There's no "goal".
  - joegaudet 13y ago
    The FPS count is generally with regards to scrolling and built in animation / transition rendering.
pyalot2 13y ago
Shadow DOM is a mechanism by which a browser can inject a subtree into the DOM, but it won't be visible to JS. This was often used for things like custom elements (inputs and such). I presume it wasn't very popular to use the shadow dom in webkit. Far as I recall, there's also talk about using the shadow dom for injecting foreign fragments into the DOM in a secure manner (web components). Although there's probably ways to achieve this without the full shadow dom.
- dasmoth 13y ago
  Shadow DOM allows the contents of a component to be styled independently from the enclosing page. As far as I can tell, there currently isn't any other good way of doing robust, scoped CSS (short of iframes). I'll be very, very, sad if shadow DOM dies.
mwenge 13y ago
It's an in-joke taking aim at Blink's stated 2014 goal of optimizing for mobile performance at the expense of supporting things like CSS Regions. Shadow DOM is also the subject of some controversy, as Blink and Mozilla seem intent on pressing ahead with implementing it without full buy-in from all vendors or even the WG.
- nephyrin 13y ago
  Mozilla (along with most everyone else) took issue with Google's intent to ship Shadow DOM. See e.g. this exchange: http://lists.w3.org/Archives/Public/www-style/2014Feb/0152.html http://lists.w3.org/Archives/Public/www-style/2014Feb/0152.h...

Can someone explain this? Isn't Shadow DOM necessary? What is this 60fps on mobile intent and how it relates to Shadow DOM?

by Geee 13y ago

Can someone explain this? Isn't Shadow DOM necessary? What is this 60fps on mobile intent and how it relates to Shadow DOM?

masklinn 13y ago

> Can someone explain this? They're finishing up the removal of unmaintained and essentially dead code which started after the Blink fork. > Isn't Shadow DOM necessary? To what? > What is this 60fps on mobile intent and how it relates to Shadow DOM? Shadow DOM requires hooks throughout the engine. If you remove the hooks (because nobody uses them because shadow dom is not supported) the engine is lighter and executes faster. Hence 60fps goal.

why_me 13y ago
> Hence 60fps goal. Is that for embedded video playback? Whatelse could it apply to? Any idea?
- 0x0 13y ago
  Wild guess: Rendering live web pages (html+js+css, with animations and scrolling) at 60 frames per second.
  - danabramov 13y ago
    As stated in nearby comments, it's an in-joke. There's no "goal".
- joegaudet 13y ago
  The FPS count is generally with regards to scrolling and built in animation / transition rendering.

pyalot2 13y ago

Shadow DOM is a mechanism by which a browser can inject a subtree into the DOM, but it won't be visible to JS. This was often used for things like custom elements (inputs and such). I presume it wasn't very popular to use the shadow dom in webkit. Far as I recall, there's also talk about using the shadow dom for injecting foreign fragments into the DOM in a secure manner (web components). Although there's probably ways to achieve this without the full shadow dom.

dasmoth 13y ago
Shadow DOM allows the contents of a component to be styled independently from the enclosing page. As far as I can tell, there currently isn't any other good way of doing robust, scoped CSS (short of iframes). I'll be very, very, sad if shadow DOM dies.

mwenge 13y ago

It's an in-joke taking aim at Blink's stated 2014 goal of optimizing for mobile performance at the expense of supporting things like CSS Regions. Shadow DOM is also the subject of some controversy, as Blink and Mozilla seem intent on pressing ahead with implementing it without full buy-in from all vendors or even the WG.

nephyrin 13y ago
Mozilla (along with most everyone else) took issue with Google's intent to ship Shadow DOM. See e.g. this exchange: http://lists.w3.org/Archives/Public/www-style/2014Feb/0152.html http://lists.w3.org/Archives/Public/www-style/2014Feb/0152.h...