From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <emacs-orgmode-bounces+larch=yhetil.org@gnu.org>
Received: from mp2 ([2001:41d0:2:bcc0::])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	by ms0.migadu.com with LMTPS
	id CHhMFZ2/i2B6YAAAgWs5BA
	(envelope-from <emacs-orgmode-bounces+larch=yhetil.org@gnu.org>)
	for <larch@yhetil.org>; Fri, 30 Apr 2021 10:28:13 +0200
Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by mp2 with LMTPS
	id qNTvEJ2/i2BtWwAAB5/wlQ
	(envelope-from <emacs-orgmode-bounces+larch=yhetil.org@gnu.org>)
	for <larch@yhetil.org>; Fri, 30 Apr 2021 08:28:13 +0000
Received: from lists.gnu.org (lists.gnu.org [209.51.188.17])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by aspmx1.migadu.com (Postfix) with ESMTPS id A011C15F1F
	for <larch@yhetil.org>; Fri, 30 Apr 2021 10:28:12 +0200 (CEST)
Received: from localhost ([::1]:37904 helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-orgmode-bounces+larch=yhetil.org@gnu.org>)
	id 1lcOVP-0001Wz-C5
	for larch@yhetil.org; Fri, 30 Apr 2021 04:28:11 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10]:38580)
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <bzg@gnu.org>) id 1lcOV4-0001Wp-7w
 for emacs-orgmode@gnu.org; Fri, 30 Apr 2021 04:27:50 -0400
Received: from fencepost.gnu.org ([2001:470:142:3::e]:59189)
 by eggs.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <bzg@gnu.org>)
 id 1lcOV4-000348-0I; Fri, 30 Apr 2021 04:27:50 -0400
Received: from [78.194.183.21] (port=36420 helo=guerry)
 by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.82) (envelope-from <bzg@gnu.org>)
 id 1lcOV2-00006d-Ss; Fri, 30 Apr 2021 04:27:49 -0400
Received: by guerry (Postfix, from userid 1000)
 id 9BB461A60EF9; Fri, 30 Apr 2021 10:27:46 +0200 (CEST)
From: Bastien <bzg@gnu.org>
To: TEC <tecosaur@gmail.com>
Subject: Re: W3C violations in Org's HTML export
In-Reply-To: <87sga4914t.fsf@gmail.com> (TEC's message of "Sat, 24 Oct 2020
 03:04:22 +0800")
Organization: GNU
Message-ID: <87eeesb57i.fsf@bzg.fr>
References: <87sga4914t.fsf@gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
Date: Fri, 30 Apr 2021 10:27:46 +0200
MIME-Version: 1.0
Content-Type: text/plain
X-BeenThere: emacs-orgmode@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org
Sender: "Emacs-orgmode" <emacs-orgmode-bounces+larch=yhetil.org@gnu.org>
X-Migadu-Flow: FLOW_IN
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org;
	s=key1; t=1619771293;
	h=from:from:sender:sender:reply-to:subject:subject:date:date:
	 message-id:message-id:to:to:cc:cc:mime-version:mime-version:
	 content-type:content-type:in-reply-to:in-reply-to:
	 references:references:list-id:list-help:list-unsubscribe:
	 list-subscribe:list-post; bh=Ca2WPuGSK+1yQoSUayvmFDGXpWbW3QkFPuPZ/M7RDLE=;
	b=r/cMJmDhNBfBbND6ALTguKzhkxCDbbbcODMTfNiN/6PTysvatxoUeUYVMZU9z8Hc9QWFeJ
	YK4XtLO87F8a87K3X1VcmwzK+PolBGF1N7YRsdQ02rht+Hu2aT8Bf53T05NJXX01HmH+El
	ZEiKgp9zmjVW6FhyMR9+lm3Oa4adCWuMvQIBHVzg+QqH79itM8/EGT34CZhBhCcfjMlYZy
	eJGs9o3/UO0pTJndQ8yR7zcZHwHcIeKqYUyoPL3pir1qs966dttahQUrZEryJ+32fHj6M+
	vC+oZCEm9dXF8hfUsASwARecExPQfjkVOFnmMMfB9BhR2WryZ3BkO5a7g5NzZQ==
ARC-Seal: i=1; s=key1; d=yhetil.org; t=1619771293; a=rsa-sha256; cv=none;
	b=Vr7/PSpn5JzefXvhNRxiuo3skB5qKoCyjBfGot6+ppjQT3LPtYt8OypjtN6Udtb2dI/6uY
	dKIiD6hXYEyv5nAMf6u3Zmh22UgboI7UMYiHeJ1+5sbNV/EM+st40mSf6mLspsIGwFHFnN
	RnzHc5YRjIJ5SvcrM0kSt3ErCJTk1mAY64MgYIp7aF8J+CD+1yZRq6Kjwj8W2WIqg+R1nR
	roSIpNSLcOZR2/HivZTkz/feCYmyVlYGiPQvxD/k4IQAmQmbGE7oi+HHSb8oaNyMBBS4Yh
	JUms9Q05aMTayDLPCF/PaVOTe73O6S5mnelQDBjZdrVWSEF82ufhB3+i5ahieA==
ARC-Authentication-Results: i=1;
	aspmx1.migadu.com;
	dkim=none;
	dmarc=pass (policy=none) header.from=gnu.org;
	spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org
X-Migadu-Spam-Score: -1.46
Authentication-Results: aspmx1.migadu.com;
	dkim=none;
	dmarc=pass (policy=none) header.from=gnu.org;
	spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org
X-Migadu-Queue-Id: A011C15F1F
X-Spam-Score: -1.46
X-Migadu-Scanner: scn0.migadu.com
X-TUID: R4Fq3Mjo2MA6

Hi Timothy,

TEC <tecosaur@gmail.com> 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 '<script type="text/javascript">' code
>   highlighting script.
>
> ** Suggestion
>    Remove the ' type="text/javascript"' part of that.

Done.

> * Error: Attribute alt not allowed on element object at this 
>   point.
>   This occurs when one has an svg figure, and one wishes to add 
>   alt text
>   (good for accessibility). This is of course applied to the 
>   <object
>   type="image/svg+xml">.
>   
>   What's interesting here is that the benefit of using an <object> 
>   over
>   an <img> for SVGs seems to basically be that it allows for a 
>   raster
>   fallback (with the downside that it is downloaded even when not
>   needed). However... if we're using HTML5, the <picture> element 
>   exists
>   for exactly this case, and provides a better implementation of
>   fallbacks. Even if one is not using HTML5, I don't see any way 
>   that
>   Org actually makes use of the potential for a raster fallback 
>   ...
>   raising the question of why an <object> is used over <img> in 
>   the
>   first place. It appears that browser support for SVGs in <img> 
>   tags
>   was originally sketchy, however that issue seems to have bee 
>   long
>   since resolved: https://caniuse.com/svg-img
>
> ** Suggestion
>    Switch <object> to <img> for SVGs, if Org does add a mechanism 
>    for
>    defining fallback images in the future, use <picture> with 
>    HTML5

Can you confirm the two issues above are already fixed?

> * 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-LH@lists.gnu.org/

I cannot reproduce this.

> * Error: Character reference expands to a control character 
>   (U+0002).
>   I have no idea where this is coming from, or why it's there --- 
>   but it
>   is, and it's not alone:
>   + Error: Character reference expands to a control character 
>   (U+001d).
>   + Error: Character reference expands to a control character 
>   (U+001f).
>   + Error: Character reference expands to a control character 
>   (U+0016).
>   + Error: Character reference expands to a control character 
>   (U+000f).
>   + Warning: Document uses the Unicode Private Use Area(s), which 
>   should
>     not be used in publicly exchanged documents. (Charmod C073)
>   + Error: Character reference expands to a control character 
>   (U+001b).
>
>   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.

> * (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:
>
>   #+begin_src org
>   ,** Features
>   @@html:<a href="features.html">@@
>   [[file:resources/img/stars.svg]]
>
>   Delve into the possibilities.
>   @@html:</a>@@
>   #+end_src
>
>   This produces the following errors:
>   + Error: End tag p seen, but there were open elements.
>   + Error: Unclosed element a.
>   + Error: End tag a violates nesting rules.
>   + Fatal Error: Cannot recover after last error. Any further 
>   errors
>     will be ignored.
>
>   It would be good to have a way to do this that doesn't cause W3C
>   issues.

Once all issues listed here are handles, please close the call for
help with "X-Woof-Help: close" as a header.

Please open a separate proposal for this.

Thanks,

-- 
 Bastien