4 ms·

By the way, there is a CSS bug in HackerNews that we discovered today[1] that is causing most of the rules to be wrongly parsed. I'm not sure if hn@ycombinator.

By the way, there is a CSS bug in HackerNews that we discovered today[1] that is causing most of the rules to be wrongly parsed. I'm not sure if hn@ycombinator.com is the proper place to report it. https://lists.mailman3.com/hyperkitty/list/dillo-dev@mailman3.com/message/MXAQDMZFGBNQLPEALQQZW5W4RR4LR27T/ https://lists.mailman3.com/hyperkitty/list/dillo-dev@mailman... Here is the bad rule: input[type=\"submit\"] { font-family:Verdana, Geneva, sans-serif; }

philipkglass 2y ago
Yes, email hn@ycombinator.com. Dang is very responsive.
dang 2y ago
Should be fixed now. Thanks!
- rodarima 2y ago
  Thanks!
- fallingsquirrel 2y ago
  5 minute bugfix, on a Saturday no less. Incredible
  - Sabinus 2y ago
    Dang is a treasure.
ptx 2y ago
And another HN bug, I think: Comments are wrapped in "span" elements (which are inline elements) but contain "p" elements (block elements) which is not valid: ......... The W3C HTML validator says: "Element p not allowed as child of element span in this context." This causes Dillo to render the text in grey from the second paragraph on.
- rodarima 2y ago
 Thanks, I reported it too by email.
 - ptx 2y ago
 I wonder if HN sticks to the current HTML markup (which is full of validation errors!) to preserve compatibility with third-party clients that scrape and parse it? In that case, maybe we could get a query parameter along the lines of "useValidMarkup=1" (or a user setting might be better) to produce valid HTML for the benefit of niche browsers that expect it while preserving the current (invalid but stable) markup by default.
 - rodarima 2y ago
 > I wonder if HN sticks to the current HTML markup (which is full of validation errors!) to preserve compatibility with third-party clients that scrape and parse it? I don't think so, but if it does I recommend they instead stick to the HTML (4.01 or 5) spec by default. > In that case, maybe we could get a query parameter along the lines of useValidMarkup=1" (or a user setting might be better) to produce valid HTML for the benefit of niche browsers that expect it while preserving the current invalid but stable) markup by default. They can guess the browser by the User-Agent and serve a "patched" version if needed (bluedwarf.top does it). But I would recommend doing against this, as it reduces the incentive for clients to get fixed and moves the responsibility to webmasters.
 - rodarima 2y ago
 Fixed at HN side (thanks dang).

philipkglass 2y ago

Yes, email hn@ycombinator.com. Dang is very responsive.

dang 2y ago

Should be fixed now. Thanks!

rodarima 2y ago
Thanks!
fallingsquirrel 2y ago
5 minute bugfix, on a Saturday no less. Incredible
- Sabinus 2y ago
  Dang is a treasure.

ptx 2y ago

And another HN bug, I think: Comments are wrapped in "span" elements (which are inline elements) but contain "p" elements (block elements) which is not valid: ......... The W3C HTML validator says: "Element p not allowed as child of element span in this context." This causes Dillo to render the text in grey from the second paragraph on.

rodarima 2y ago
Thanks, I reported it too by email.
- ptx 2y ago
  I wonder if HN sticks to the current HTML markup (which is full of validation errors!) to preserve compatibility with third-party clients that scrape and parse it? In that case, maybe we could get a query parameter along the lines of "useValidMarkup=1" (or a user setting might be better) to produce valid HTML for the benefit of niche browsers that expect it while preserving the current (invalid but stable) markup by default.
  - rodarima 2y ago
    > I wonder if HN sticks to the current HTML markup (which is full of validation errors!) to preserve compatibility with third-party clients that scrape and parse it? I don't think so, but if it does I recommend they instead stick to the HTML (4.01 or 5) spec by default. > In that case, maybe we could get a query parameter along the lines of useValidMarkup=1" (or a user setting might be better) to produce valid HTML for the benefit of niche browsers that expect it while preserving the current invalid but stable) markup by default. They can guess the browser by the User-Agent and serve a "patched" version if needed (bluedwarf.top does it). But I would recommend doing against this, as it reduces the incentive for clients to get fixed and moves the responsibility to webmasters.
    - rodarima 2y ago
      Fixed at HN side (thanks dang).