00:00
<cvazac>
should a cross-origin request (that happens to be for an IFRAME) be visible by a service worker?
07:38
<annevk>
Nope
13:34
<Nepose>
Hello :)
13:35
<Nepose>
Let me please know, I have one idea about HTML standard and I wanted to ask other people if it's not too stupid, where could I put it?
14:11
<Nepose>
And are we able to suggest new standards? I mean completely new, like XML that you don't have ;)
15:17
<annevk>
Nepose: https://whatwg.org/faq might help
15:21
<Nepose>
annevk: thanks, this helped me :) but not fully, the problem is that my idea is connected both to XML and HTML and I see that you don't maintain XML standard, are you going to do anything with it?
15:25
<annevk>
Nepose: extensions to XML seem unlikely, though I hold out some hope for XML5
15:26
<annevk>
Nepose: note that the HTML Standard does say a few things about XML and has made some changes
15:34
<Nepose>
annevk: honestly I've never heard about XML5, but now found and it seems to be a great thing, I wanted to suggest possibility to use boolean attributes like in HTML5
15:35
<annevk>
Ah, that would indeed enable that
15:35
<Nepose>
about XHTML: now we have HTML (5?) and XHTML, my idea is to use only XHTML and enhance XML to allow stuff from HTML5 like boolean attributes, document.write(), noscript tag
15:36
<Nepose>
for example as XML 2.0 or XML5 as you sent me
15:36
<annevk>
I don’t think we want to spread document.write() any further
15:38
<Nepose>
And this thing I wrote here would also bring to HTML namespaces, self-closed script tag, XSL Transformations if someone wants to use it
15:38
<Nepose>
Of course it is available now but not common
15:39
<Nepose>
And in current XML serialization of HTML5 named character entities can't be used unfortunately
15:42
<Nepose>
Oh and the thing I've forgotten to: allowing <?xml-model href="..." schematypens="..." (...) ?> instruction from current working group note would be also great in XML5 / XML 2.0
15:46
<Nepose>
In my opinion proposing one language as living standard is just easier and less complicated instead having two ones, but one of it almost not known. HTML as XML application for XML5 would in my idea allow everything which exists now in HTML5 and enhance it with possibility to use other XML applications and XSL stylesheets inside document if someone wants
15:46
<Nepose>
Let me please know, does it have any sense for you?
17:55
<Domenic>
I think generally the community is not in favor of evolving XML much further. We're instead doing our best to limit its spread and eventually remove it from browsers by merging it with the HTML parser, if at all possible. It's not clear that'll ever work out, but maintaining two separate formats for documents on the web is a large maintenance burden, and the most common libraries for parsing and manipulating XML
17:55
<Domenic>
(libxml/libxslt) are bug-ridden and full of security holes.
18:54
<Nepose>
@Domenic: thanks for response (found in the channel log) :) but anyway, do you consider any future for HTML5 as XML application?
18:54
<Nepose>
and does XML5 have any chances to be done?
18:57
<Domenic>
Nepose: I don't know what "any future for HTML as XML application" means.
18:58
<Domenic>
As for XML5, that's part of the plan to get rid of XML, so maybe it will happen, but I haven't seen much movement so far.
18:59
<Nepose>
By this phrase I meant if WHATWG is going to develop this later together with "normal", non-XML-based version of HTML LS
19:00
<Nepose>
XHTML was before (when 1.0 / 1.1) an XML application, but I'm not sure if this phrase is actual now
19:24
<Domenic>
These days we just have to support a way of parsing XML into a DOM tree for backward compatibility, basically. I don't know much about XML applications.
20:40
<Nepose>
Domenic: okay, I'll try to ask also other people and show them example of what I mean, thanks