| 05:12 | <muan> | Hi. In investigating implementation details for SFNSP I noticed an interop issue.
Does this warrant a WPT or perhaps a clarifying issue in HTML on what should/shouldn't happen? |
| 05:14 | <Domenic> | I think it is known that there is a connection between focus and selection in some browsers but not others, and this is an interop issue but also one that browsers feel is kind of a quality differentiator. |
| 05:15 | <Domenic> | https://github.com/whatwg/html/issues/7657 |
| 05:15 | <Domenic> | https://github.com/whatwg/html/issues/7759 |
| 05:16 | <Domenic> | If Chrome is the odd one out, maybe it's worth asking the relevant people if they want to change. But my impression was that Chrome thought it was better for users to have these concepts be separate, and the spec allows them to be separate. |
| 05:17 | <Domenic> | This is a similar interop issue to how, e.g., Safari chooses to make lots of controls not-focusable by default, and the spec allows that. |
| 05:21 | <muan> | I see. Thanks. |
| 07:13 | <annevk> | Is there a way to style an element differently based on the scroll position in CSS? E.g., once the end user has scrolled down for x pixels, style the element differently? |
| 09:55 | <martin> | Is there a way to style an element differently based on the scroll position in CSS? E.g., once the end user has scrolled down for x pixels, style the element differently? |
| 09:57 | <martin> | Is there a name for the HTML elements that were created by the parser because they didn't exist? (only happens for html, head, body, p, colgroup, tbody and tr) |
| 10:14 | <martin> | Is there a name for the HTML elements that were created by the parser because they didn't exist? (only happens for html, head, body, p, colgroup, tbody and tr) |
| 12:45 | <muan> | does summary count |
| 12:59 | <sideshowbarker> | does summary count summary isn’t created by the parser |
| 13:01 | <sideshowbarker> | Is there a name for the HTML elements that were created by the parser because they didn't exist? (only happens for html, head, body, p, colgroup, tbody and tr) |
| 13:03 | <annevk> | When is <p> implied? |
| 13:03 | <annevk> | Also, today I learned you can omit the first <tr>, though I guess that's non-compliant? |
| 13:04 | <sideshowbarker> | yeah, as far as document conformance |
| 15:01 | <martin> | in the conceptual model for HTML those elements do exist in the document — it’s just that their start tags and end tags are omitted in the source markup |
| 15:02 | <martin> | for </p> in body insertion mode if it wasn't opened previously |
| 15:12 | <Jeffrey Yasskin> | Is there a way to style an element differently based on the scroll position in CSS? E.g., once the end user has scrolled down for x pixels, style the element differently? |
| 16:37 | <Matrix_heisemberg tuco> | hey mi friends |
| 16:37 | <Matrix_heisemberg tuco> | some body is hacking my pc and phone please help me |
| 16:38 | <Matrix_heisemberg tuco> | pleaseee |
| 16:39 | <Matrix_heisemberg tuco> | i access here just because im clicking and cliking |
| 16:40 | <Matrix_heisemberg tuco> | its all ready like 2 monts i trying to block or eraese this people from mi acounts |
| 16:40 | <Matrix_heisemberg tuco> | they ha access to all my info |
| 16:40 | <Matrix_heisemberg tuco> | plaseeeeee |
| 16:41 | <Matrix_heisemberg tuco> | im beging you gus |
| 16:41 | <Matrix_heisemberg tuco> | guys |
| 16:44 | <Matrix_heisemberg tuco> | all ready lost my job for this delincuents |
| 16:48 | <Matrix_heisemberg tuco> | Im desesperate PLEASEEEE |
| 17:05 | <Matrix_heisemberg tuco> | REALLY NOBODY? |
| 17:05 | <Matrix_heisemberg tuco> | they supost to be white hats or something like that |
| 17:08 | <Matrix_heisemberg tuco> | i dont know what is all this |
| 17:41 | <Matrix_heisemberg tuco> | wow so are the same ??? |