Re: [whatwg] menuitem: Issue reported by the web developers
On Wed, 26 Nov 2014 07:24:31 +0100, Ian Hickson i...@hixie.ch wrote: On Wed, 26 Nov 2014, Sanjoy Pal wrote: As per specification [1][2], menuitem should not have end tag, but few websites uses menuitemSome markup/menuitem which resulted in broken sites[3][4]. Firefox allows menuitemSome markup/menuitem. So, we are wondering if specification can be modified to allow menuitemSome markup/menuitem for backward compatibility. Do we know how many sites are affected? As I see it there's basically three choices -- in my order of preference, they would be: - break the sites: if there aren't many, and especially if they can be evangelised to avoid these mistakes, then we should just do that - rename menuitem to something else, like command: this would be unfortunate, since the feedback from Mozilla a few years ago was that they'd rather have menuitem than command, and it would also mean some parser churn, which is always bad, but it would probably be reasonably safe to do if we can find a good replacement element name - change menuitem's semantics so that the label comes from the element's textContents instead of a label= attribute (and charge the parser accordingly): not sure how compatible this would be; it has numerous disadvantages, too, like making people think they can put markup in the element (look at the Apple page for an example), which wouldn't work There may be other options that aren't immediately coming to mind. - Make the end tag optional and have menuitem, menu and hr generate implied /menuitem end tags. (Maybe other tags like li and p can also imply /menuitem.) The label attribute be honored if specified, otherwise use the textContent with leading and trailing whitespace trimmed. This would allow either syntax unless I'm missing something. -- Simon Pieters Opera Software
[whatwg] question to usage of sub and mark elements
Hello,
is it recommendet to use the sup element to point to footnotes -may be with
an class extension or without-, like below:
article
ptext text textsup class=footnotes*/sup
footer
* bla bla bla
/footer
/article
Second question, is it recommendet to use the mark element similar to usage
of permanent markers in books, also probably with class-Attributes.
The text is german, but do not care, think of the content of article is
similar to a site of a book, and the footer is the below part of the same
site:
style .notizen{background: anyNeonColor;}style
article
blockquote cite=http://t3n.de/news/html5-fertig-575078/;
h2Der schönste Tag eures Lebens: W3C stellt HTML5 fertigh2
p... ... .../p
pmark class=notizenMit der Standardisierung von HTML5 hat
sich das Leben von Entwicklern schlagartig vereinfacht */mark,
und eine neue Ära wurde eingeleitet./p
time datetime=2014-10-2929.10.2014/time
/blockquote
footer
pEntweder hat der Verfasser dieses Artikels keinen blassen Schimmer
was er da schreibt oder ich habe etwas verpasst!!!p
/footer
/article
Please give us much more examples for usage scenario
http://www.dict.cc/englisch-deutsch/scenario.htmls in the reccomondation
or other relevant docs.
I would be glad for a response, even a short one.
Thanks
Re: [whatwg] relationship between labeled control and label for :active and :hover pseudos
On 10 Nov 2014, at 15:23, Florian Rivoal flor...@rivoal.net wrote: I suggest making this propagation of the :hover and :active state between label and labeled control bidirectional for both :hover and :active. On 10 Nov 2014, at 16:38, Boris Zbarsky bzbar...@mit.edu wrote: The label, or the labels? The problem of hover the control if the label is hovered is simple: the label already has a reference to the control it's labeling; when an element enters hover state you at worst have to deal with one other element (plus their ancestors) entering hover state. And even that gets a bit complicated given the ancestors thing. The backreference, however, is a one-to-many relationship, which makes things quite complicated, or fairly slow, or both, when multiple labels label the same form control. So I would be a bit careful here. On 14 Nov 2014, at 21:34, Ryosuke Niwa rn...@apple.com wrote: I don’t find it compelling to natively support this behavior in the browser. As selectors is a CSS topic as much as an HTML one, I brought this to the CSS working group (mailing list then telecon) for further discussion to see if its members thought this was worth pursuing or not before coming back here. The group made a resolution agreeing that :hover and :active should be made to propagate bidirectionally between labels and labeled controls, as the behaviour was found useful, and the performance question not problematic. Since you raised specific concerns about performance, Microsoft, who already implements this, went through their bug database to check: “there is not a single bug filed against IE regarding performance issues by tying the the label to the labeled control”. I also made a test case with a silly amount of labels plus some nesting. I am running IE(10) in a VM, and there’s no noticeable delay. http://jsbin.com/juzusopapu/1/watch?html,css,output Out of people who explicitly gave opinions, Google (Tab Atkins), Microsoft (Greg Whitworth), and Fantasai were for it, while Mozilla (David Baron Tantek Çelik) were fine with in. No one raised objections. - Florian
Re: [whatwg] menuitem: Issue reported by the web developers
On Wed, 26 Nov 2014, Simon Pieters wrote: - Make the end tag optional and have menuitem, menu and hr generate implied /menuitem end tags. (Maybe other tags like li and p can also imply /menuitem.) The label attribute be honored if specified, otherwise use the textContent with leading and trailing whitespace trimmed. This would allow either syntax unless I'm missing something. That's another option, yeah. Probably the best so far if we can't just power through and break the sites in question. It's not yet clear to me how many sites we're talking about here and how possible it is to evaneglise them. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
