New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate public identifiers extensions spec? #259

Open
travisleithead opened this Issue Apr 25, 2016 · 7 comments

Comments

Projects
None yet
4 participants
@travisleithead
Member

travisleithead commented Apr 25, 2016

At the end of: https://www.w3.org/Bugs/Public/show_bug.cgi?id=13409 which was cloned from: https://www.w3.org/Bugs/Public/show_bug.cgi?id=20769, the proposal was taken to a [very short] extension specification that adds a new DTD to the list of DTDs for the purpose of getting adoption for XHTML documents.

http://www.w3.org/2003/entities/2007doc/xhtmlpubid.html

Is there interest in merging this into HTML5.1, or does it need incubation (at WICG) first?

@davidcarlisle

This comment has been minimized.

Show comment
Hide comment
@davidcarlisle

davidcarlisle commented Apr 25, 2016

See also

whatwg/html#500

@chaals

This comment has been minimized.

Show comment
Hide comment
@chaals

chaals May 10, 2016

Collaborator

Without someone to test implementations, this is at risk for the 5.1 CR

Collaborator

chaals commented May 10, 2016

Without someone to test implementations, this is at risk for the 5.1 CR

@travisleithead

This comment has been minimized.

Show comment
Hide comment
@travisleithead

travisleithead May 24, 2016

Member

Add pointer to this doc from HTML.

Member

travisleithead commented May 24, 2016

Add pointer to this doc from HTML.

@travisleithead

This comment has been minimized.

Show comment
Hide comment
@travisleithead

travisleithead May 25, 2016

Member

After investigation, it looks like the latest proposal that has some agreement in whatwg/html#500 is not inline with the published version of the extension spec: http://www.w3.org/2003/entities/2007doc/xhtmlpubid.html, so a pointer to that document is likely insufficient.

As I understand it, the latest proposal is to add new SYSTEM identifier processing logic (note: the existing list is for PUBLIC identifiers) to handle the case-sensitive term mathml.dtd or a FPI with suffix /mathml.dtd and use that to trigger the spec's existing entity list (the embedded data:uri), which brings unity to the force, err, unity for entity handling anyway.

I'll create some tests to see how this will behave...

Member

travisleithead commented May 25, 2016

After investigation, it looks like the latest proposal that has some agreement in whatwg/html#500 is not inline with the published version of the extension spec: http://www.w3.org/2003/entities/2007doc/xhtmlpubid.html, so a pointer to that document is likely insufficient.

As I understand it, the latest proposal is to add new SYSTEM identifier processing logic (note: the existing list is for PUBLIC identifiers) to handle the case-sensitive term mathml.dtd or a FPI with suffix /mathml.dtd and use that to trigger the spec's existing entity list (the embedded data:uri), which brings unity to the force, err, unity for entity handling anyway.

I'll create some tests to see how this will behave...

@travisleithead

This comment has been minimized.

Show comment
Hide comment
@travisleithead

travisleithead May 27, 2016

Member

Wrote tests for all the DTD defs for XHTML docs in the spec: web-platform-tests/wpt#3081

Member

travisleithead commented May 27, 2016

Wrote tests for all the DTD defs for XHTML docs in the spec: web-platform-tests/wpt#3081

@travisleithead

This comment has been minimized.

Show comment
Hide comment
@travisleithead

travisleithead May 27, 2016

Member

Also tested (and commented out) the proposed syntax. The tests show that:

  • Edge: tends to eat the entity references when parsed in XHTML ???
  • Chrome: only seems to have trouble with & < <⃒ and the -//W3C//DTD MathML 2.0//EN string isn't recognized.
  • Firefox: had trouble only with ⃜ ̑ ⃛ ⃛ and that was it!

Didn't test Safari.

Of course, the proposed new syntax doesn't work in any current browser at the moment. Given this, rather than take this change (which is probably good) now for 5.1 I propose moving this fix to "After 5.1" so that we can get some interoperable support behind it after it is put into the 5.2 editor's draft (it may go into the WHATWG spec first, which is fine).

Member

travisleithead commented May 27, 2016

Also tested (and commented out) the proposed syntax. The tests show that:

  • Edge: tends to eat the entity references when parsed in XHTML ???
  • Chrome: only seems to have trouble with & < <⃒ and the -//W3C//DTD MathML 2.0//EN string isn't recognized.
  • Firefox: had trouble only with ⃜ ̑ ⃛ ⃛ and that was it!

Didn't test Safari.

Of course, the proposed new syntax doesn't work in any current browser at the moment. Given this, rather than take this change (which is probably good) now for 5.1 I propose moving this fix to "After 5.1" so that we can get some interoperable support behind it after it is put into the 5.2 editor's draft (it may go into the WHATWG spec first, which is fine).

@travisleithead

This comment has been minimized.

Show comment
Hide comment
@travisleithead

travisleithead Jun 1, 2016

Member

Per short IRC discussion, this does not appear to be a blocking issue for 5.1, so moving to 5.2.

Member

travisleithead commented Jun 1, 2016

Per short IRC discussion, this does not appear to be a blocking issue for 5.1, so moving to 5.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment