Re: W3C violations in Org's HTML export
On Fri, Oct 23, 2020 at 3:46 PM TEC wrote: > ** Suggestion >Make the subtitle an independent element, is can still be a >p.subtitle, just not /inside/ the h2 title Have you seen this? Suggests wrapping title h* and p within a header. https://www.w3.org/TR/html52/common-idioms-without-dedicated-elements.html#subheadings-subtitles-alternative-titles-and-taglines Bruce
Re: W3C violations in Org's HTML export
Bastien writes: >> ** Suggestion >>Make the subtitle an independent element, is can still be a >>p.subtitle, just not /inside/ the h2 title > > Agreed, can you provide a patch for this? I'll add that to my todo list. >> ** Suggestion >>Remove the ' type="text/javascript"' part of that. > > Done. Nice. >> [SVGs] > Can you confirm the two issues above are already fixed? As of d96e897579 I'm not seeing any more W3C complaints :) >> * Error: Duplicate ID org0424ed6. >> Clearly, this can happen. I'm not sure how. >> I'd like to draw attention to this email I sent a while ago >> (excuse >> the mangled start) >> https://orgmode.org/list/e1jxajq-0004dk...@lists.gnu.org/ > > I cannot reproduce this. This may have been a low-chance once off / short-lived strange bug. If nobody else has seen this happen, I'd be inclined to dismiss this. >> * Error: Character reference expands to a control character >> (U+0002). >> >> I suspect this may be htmlize, but I'm not sure, and it's >> Org-related, >> so I'll include it. > > I don't observe this, a reproducible recipe is welcome. I'll come back to this if I can find out more. >> * (not an error) Difficulty in 'wrapping' sections >> It's quite reasonable (IMO) to want to wrap a (sub*)section in a >> certain element, such as a link. Indeed I've wanted to do this >> to create clickable 'cards' on the homepage of my org website >> revamp. Unfortunately there doesn't seem to be any property like >> :HTML_WRAP: etc. that can be applied, forcing me to try this: >> [...] > > Please open a separate proposal for this. Will do once I've thought a bit about what would be a good interface/implementation for this. > Once all issues listed here are handles, please close the call for > help with "X-Woof-Help: close" as a header. Will do Thanks for reminding me about this, Timothy.
Re: W3C violations in Org's HTML export
Hi Timothy, TEC writes: > * Error: Element p not allowed as child of element h2 in this > context > Org currently seems to put a p.subtitle inside the heading. > This violates the "phrasing content" restriction. > > https://html.spec.whatwg.org/multipage/sections.html#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements > > ** Suggestion >Make the subtitle an independent element, is can still be a >p.subtitle, just not /inside/ the h2 title Agreed, can you provide a patch for this? > * Warning: The type attribute is unnecessary for JavaScript > resources. > This seems to be from the
Re: W3C violations in Org's HTML export
Hi Timothy, TEC writes: > I don't think this should be forgotten about, so I'm adding it to > https://updates.orgmode.org/#help for now. Thanks - a tip: you can use a summary like this one with Woof: X-Woof-Help: Fix W3C violations in Org's HTML export See https://github.com/bzg/woof#annotations-for-bugs-and-help-requests Also, feel free to submit patches for these issues, ideally by discussing them in separate threads. -- Bastien
Re: W3C violations in Org's HTML export
I don't think this should be forgotten about, so I'm adding it to https://updates.orgmode.org/#help for now.
Re: W3C violations in Org's HTML export
Hi Timothy, TEC writes: > In developing my take on the Org website and my coFig file, it has > come to my attention that there seem to be a few W3C violations in > the HTML export. thanks for the careful tests and for reporting this. > I always export with these settings, > which may affect some of the items below. > > #+begin_src emacs-lisp > (setq org-html-doctype "html5" > org-html-html5-fancy t) > #+end_src I suggest we first try to fix HTML errors that we have with the default settings, then errors with fancy ones. > That's all that I could see on a first glance. I'm hoping that > documenting these issues here will be the first step to solving > them. It surely does. Can you provide a patch for each issue, opening a new thread so that we can discuss the solution? Thanks! -- Bastien
W3C violations in Org's HTML export
Hi everyone, In developing my take on the Org website and my coFig file, it has come to my attention that there seem to be a few W3C violations in the HTML export. I always export with these settings, which may affect some of the items below. #+begin_src emacs-lisp (setq org-html-doctype "html5" org-html-html5-fancy t) #+end_src * Error: Element p not allowed as child of element h2 in this context Org currently seems to put a p.subtitle inside the heading. This violates the "phrasing content" restriction. https://html.spec.whatwg.org/multipage/sections.html#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements ** Suggestion Make the subtitle an independent element, is can still be a p.subtitle, just not /inside/ the h2 title * Warning: The type attribute is unnecessary for JavaScript resources. This seems to be from the
