Re: [whatwg] : Issue reported by the web developers

[Simon Pieters]

On Wed, 07 Oct 2015 07:12:16 +0200, Anne van Kesteren   
wrote:



On Wed, Nov 26, 2014 at 9:50 AM, Simon Pieters  wrote:

Make the end tag optional and have ,  and  generate
implied  end tags. (Maybe other tags like  and  can  
also
imply .) 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.


File an issue on doing this?


Filed https://github.com/whatwg/html/issues/234 and  
https://github.com/whatwg/html/issues/235



Are Firefox and Chrome (behind a flag) implementing this feature
identical otherwise? Anything they don't implement from the 
setup? It seems at this point we should cut our losses and remove
unimplemented markup features and defer to custom elements for the
foreseeable future.





--
Simon Pieters
Opera Software

Re: [whatwg] : Issue reported by the web developers

[Anne van Kesteren]

On Wed, Nov 26, 2014 at 9:50 AM, Simon Pieters  wrote:
> Make the end tag optional and have ,  and  generate
> implied  end tags. (Maybe other tags like  and  can also
> imply .) 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.

File an issue on doing this?

Are Firefox and Chrome (behind a flag) implementing this feature
identical otherwise? Anything they don't implement from the 
setup? It seems at this point we should cut our losses and remove
unimplemented markup features and defer to custom elements for the
foreseeable future.


-- 
https://annevankesteren.nl/

Re: [whatwg] : Issue reported by the web developers

[Tab Atkins Jr.]

So, here's one example of a page putting content inside of :
https://developer.apple.com/library/prerelease/ios/documentation/HealthKit/Reference/HealthKit_Constants/index.html#//apple_ref/c/econst/HKBodyTemperatureSensorLocationRectum

If you use Chrome with the Experimental Web Platform Features flag
turned on (so we actually parse , rather than it being
parsed as an unknown element), you'll see a ton of crap overlaying the
page from the s.  I'm leaning pretty heavily toward this being a
coincidental name collision; that is, it looks like they're
intentionally unknown elements that happen to be named
/; the markup has no relation whatsoever to what is
specced.

~TJ

Re: [whatwg] : Issue reported by the web developers

[Simon Pieters]

On Mon, 08 Dec 2014 21:50:56 +0100, Simon Pieters  wrote:


On Thu, 27 Nov 2014 01:15:20 +0100, Ian Hickson  wrote:


On Wed, 26 Nov 2014, Simon Pieters wrote:


- Make the end tag optional and have ,  and 
generate implied  end tags. (Maybe other tags like  and
 can also imply .) 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.


In httparchive  
http://bigqueri.es/t/analyzing-html-css-and-javascript-response-bodies/442  
:


FTR, the numbers were slightly wrong. I didn't count top-level pages, I  
counted resources (including e.g. iframes). Also there is a bug in the  
data with duplicate entries for some pages  
(https://twitter.com/zcorpan/status/542363458671747072 ).



* 10101 pages use 


8929 pages use 

SELECT page, COUNT(*) as num
FROM [httparchive:runs.2014_08_15_requests_body]
WHERE mimeType CONTAINS "html"
  AND REGEXP_MATCH(LOWER(body), r'
* 39 have no label attribute
* 0 have non-whitespace content
* 15 have no end tag

Based on this, it seems possible to keep it as a void element and only  
use the label attribute.



SELECT COUNT(*) as num,
  CASE
   WHEN REGEXP_MATCH(LOWER(body), r']+\s)?label\s*=')  
THEN "label present"

   ELSE "no label"
  END as stat
 FROM [httparchive:runs.2014_08_15_requests_body]
WHERE mimeType CONTAINS "html"
   AND REGEXP_MATCH(LOWER(body), r'

8900 have label present (so 29 no label).

SELECT page, COUNT(*) as num
FROM [httparchive:runs.2014_08_15_requests_body]
WHERE mimeType CONTAINS "html"
  AND REGEXP_MATCH(LOWER(body), r']+\s)?label\s*=')
GROUP BY page
ORDER BY num desc



SELECT COUNT(*) as num,
  CASE
   WHEN REGEXP_MATCH(LOWER(body),  
r']*>(\s*[^<]+)+\s*') THEN "has content"

   ELSE "no content"
  END as stat
 FROM [httparchive:runs.2014_08_15_requests_body]
WHERE mimeType CONTAINS "html"
   AND REGEXP_MATCH(LOWER(body), r'') THEN "end tag"
   ELSE "no end tag"
  END as stat
 FROM [httparchive:runs.2014_08_15_requests_body]
WHERE mimeType CONTAINS "html"
   AND REGEXP_MATCH(LOWER(body), r'


--
Simon Pieters
Opera Software

Re: [whatwg] : Issue reported by the web developers

[Simon Pieters]

On Mon, 08 Dec 2014 21:50:56 +0100, Simon Pieters  wrote:


SELECT COUNT(*) as num,
  CASE
   WHEN REGEXP_MATCH(LOWER(body),  
r']*>(\s*[^<]+)+\s*') THEN "has content"

   ELSE "no content"
  END as stat
 FROM [httparchive:runs.2014_08_15_requests_body]
WHERE mimeType CONTAINS "html"
   AND REGEXP_MATCH(LOWER(body), r'

Hixie pointed out that this doesn't catch element children. So flipping it  
gives:


SELECT COUNT(*) as num,
 CASE
  WHEN REGEXP_MATCH(LOWER(body), r']*>\s*') THEN  
"no content"

  ELSE "has content"
 END as stat
FROM [httparchive:runs.2014_08_15_requests_body]
WHERE mimeType CONTAINS "html"
  AND REGEXP_MATCH(LOWER(body), r'15 of these are omitting the end tag, as seen by the other query. So what  
is the last one doing?


SELECT url,body
FROM [httparchive:runs.2014_08_15_requests_body]
WHERE mimeType CONTAINS "html"
  AND LOWER(body) CONTAINS ']*>\s*')

Row url body
1	http://www.dod.gr/lib/menuData_v483.php	
 community.swf  
community ...


Yep, mislabeled XML.

For completeness, the 15 pages with no end tags fall in two categories:

* for(i=0;i* 'complete') spm_initMyMenu(this,  
spm_getById('dnn_dnnMENU_ctldnnMENU'))"">title=""صفحه اصلی"" url=""/Default.aspx?tabid=2533"" lefthtml="""" css="" "" />



Previous conclusion stands. :-)

--
Simon Pieters
Opera Software

Re: [whatwg] : Issue reported by the web developers

[Simon Pieters]

On Mon, 08 Dec 2014 21:50:56 +0100, Simon Pieters  wrote:


On Thu, 27 Nov 2014 01:15:20 +0100, Ian Hickson  wrote:


On Wed, 26 Nov 2014, Simon Pieters wrote:


- Make the end tag optional and have ,  and 
generate implied  end tags. (Maybe other tags like  and
 can also imply .) 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.


In httparchive  
http://bigqueri.es/t/analyzing-html-css-and-javascript-response-bodies/442  
:


A related issue that has come up is  vs type=popup>.


* 10070 pages use 
* 0 pages use 
* 100 pages use  or some other value

https://groups.google.com/a/chromium.org/d/msg/blink-dev/MkEDloT-yu8/wJhIK6jVSXMJ

Based on this I suggest we rename popup to context in the spec.

--
Simon Pieters
Opera Software

Re: [whatwg] : Issue reported by the web developers

[Simon Pieters]

On Thu, 27 Nov 2014 01:15:20 +0100, Ian Hickson  wrote:


On Wed, 26 Nov 2014, Simon Pieters wrote:


- Make the end tag optional and have ,  and 
generate implied  end tags. (Maybe other tags like  and
 can also imply .) 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.


In httparchive  
http://bigqueri.es/t/analyzing-html-css-and-javascript-response-bodies/442  
:


* 10101 pages use 
* 39 have no label attribute
* 0 have non-whitespace content
* 15 have no end tag

Based on this, it seems possible to keep it as a void element and only use  
the label attribute.



SELECT COUNT(*) as num,
 CASE
  WHEN REGEXP_MATCH(LOWER(body), r']+\s)?label\s*=') THEN  
"label present"

  ELSE "no label"
 END as stat
FROM [httparchive:runs.2014_08_15_requests_body]
WHERE mimeType CONTAINS "html"
  AND REGEXP_MATCH(LOWER(body), r'  WHEN REGEXP_MATCH(LOWER(body),  
r']*>(\s*[^<]+)+\s*') THEN "has content"

  ELSE "no content"
 END as stat
FROM [httparchive:runs.2014_08_15_requests_body]
WHERE mimeType CONTAINS "html"
  AND REGEXP_MATCH(LOWER(body), r'') THEN "end tag"
  ELSE "no end tag"
 END as stat
FROM [httparchive:runs.2014_08_15_requests_body]
WHERE mimeType CONTAINS "html"
  AND REGEXP_MATCH(LOWER(body), r'

Re: [whatwg] : Issue reported by the web developers

[Ian Hickson]

On Wed, 26 Nov 2014, Simon Pieters wrote:
>
> - Make the end tag optional and have ,  and  
> generate implied  end tags. (Maybe other tags like  and 
>  can also imply .) 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.   `._.-(,_..'--(,_..'`-.;.'

Re: [whatwg] : Issue reported by the web developers

[Simon Pieters]

On Wed, 26 Nov 2014 07:24:31 +0100, Ian Hickson  wrote:


On Wed, 26 Nov 2014, Sanjoy Pal wrote:


As per specification [1][2],  should not have end tag, but few
websites uses Some markup which resulted in broken
sites[3][4].

Firefox allows Some markup. So, we are wondering if
specification can be modified to allow Some markup
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  to something else, like : this would be
unfortunate, since the feedback from Mozilla a few years ago was that
they'd rather have  than , 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 '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 ,  and  generate  
implied  end tags. (Maybe other tags like  and  can also  
imply .) 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

Re: [whatwg] : Issue reported by the web developers

[Ian Hickson]

On Wed, 26 Nov 2014, Sanjoy Pal wrote:
> 
> As per specification [1][2],  should not have end tag, but few 
> websites uses Some markup which resulted in broken 
> sites[3][4].
> 
> Firefox allows Some markup. So, we are wondering if 
> specification can be modified to allow Some markup 
> 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  to something else, like : this would be 
unfortunate, since the feedback from Mozilla a few years ago was that 
they'd rather have  than , 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 '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.

-- 
Ian Hickson   U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

[whatwg] : Issue reported by the web developers

[Sanjoy Pal]

Hello Friends,

 

We have implemented contextmenu attribute in blink as per the specification.

There is an issue reported by the web developers.

 

As per specification [1][2],  should not have end tag, but few
websites uses Some markup which resulted in broken
sites[3][4].

Firefox allows  Some markup. So, we are wondering if
specification can be modified to allow Some markup for
backward compatibility.

 

Please provide your guidance on the same.

 

 

[1] 
https://html.spec.whatwg.org/multipage/forms.html#the-menuitem-element

[2] 
https://html.spec.whatwg.org/multipage/syntax.html#void-elements

[3]https://crbug.com/412945

[4]https://crbug.com/434240

 

 

Thanks and regards,

Sanjoy Pal