W3C home > Mailing lists > Public > public-html@w3.org > November 2014

Re: suggestion for tag set <sarcasm> </sarcasm> pair

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Mon, 3 Nov 2014 23:52:50 +0000
Message-ID: <CA+ri+VnsATdx9Xw+Cow8A_jRbEw=ASBoJ-7-dt=Dj+4ZuqrxJQ@mail.gmail.com>
To: "Jukka K. Korpela" <jukka.k.korpela@kolumbus.fi>
Cc: Pradeep Kumar <pradeep.online00@gmail.com>, sam <sdomenic@comcast.net>, HTMLWG WG <public-html@w3.org>
On 3 November 2014 12:32, Jukka K. Korpela <jukka.k.korpela@kolumbus.fi>
wrote:

> Your techniques do not work in Chrome.


right, tracked down as a chrome bug.
https://code.google.com/p/chromium/issues/detail?id=393490

You can set attributes to HTML elements in JavaScript. Whether such a
> specific setting is of any help is highly questionable; expressing sarcasm
> that way is about as enigmatic as it is to express it with leading and
> trailing Arabic question marks (which is what “؟” really is; the reversed
> question mark is “⸮”).
>

sure, what you get with a custom element, is that the semantics are added
for you.
FYI I Asked a few friends who are screen reader users. they found the info
useful.
Now using the correct reverse question mark, THANKS!

Besides <sarcasm> is an exercise in suggesting we don't need a native
element for everything and if one really wants an element , then it can be
done using newer features of the open web platform, if one so desires.
Whether it is worthwhile, is in the eyes of the developer, and not
constrained by the stated tastes of commentators.
--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
Received on Monday, 3 November 2014 23:53:57 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:46:11 UTC