- From: <bugzilla@jessica.w3.org>
- Date: Tue, 10 May 2016 15:43:43 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29608 --- Comment #4 from Michael Kay <mike@saxonica.com> --- Noted in discussion: (a) this is a new feature to introduce at a late stage and because of the interaction with the environment there's a lot of scope for quibbling about the exact spec; the chance of getting it right first time is small. (b) doc() currently allows a fragment id and defines no semantics for it. Almost any attempt to define semantics for it would cause a compatibility problem for some implementations (or for their users...) (c) unparsed-text() currently disallows a fragment id. If we were to allow it, we would probably have to leave the semantics implementation-defined if we want similar behaviour to doc(). It's not clear that's desirable. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 10 May 2016 15:43:45 UTC