Re: [w3c/webcomponents] Should parser extensibility be a design goal? (#113)

>From ad-hoc reducing `httparchive` starting with all funny-looking characters on my keyboard, removing characters where the matches include things like regexps or scripts or other stuff, I was left with only `!` (76 matches) and `|` (60 matches) as possible sigils.

Some have `!` or `|` as the last character of an unquoted attribute value, like
```
<img src=/static/yeoman-character-sticker.c30c59fb9e.png class=Donation-sticker width=190 height=294 alt=Stickers!>
```

view-source:http://www.aujourdhui-en-france.fr/
uses `<div ... !>` and expects non-void.

view-source:http://ww1.jaruratmand.com/
uses `<meta name=description content=This website is for sale! ... We hope you find what you are searching for!>` (void)

view-source:http://gongbe.com/
uses `<a ... |>` and expects non-void.

view-source:http://www.philipmorrisdirect.co.uk/
uses `<img |>` (void)

None of the matches had element names with `-` in them.

For either of these, a space before it is required because otherwise the character becomes part of the element name or attribute name. The sigil could be `/!` or `/|`though I suppose that's pretty ugly.

In order to not break pages like the ones above, I suggest any sigil to change parser behavior be limited to elements that have `-` in the name.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/113#issuecomment-211376562