On Sat, Dec 13, 2008 at 1:40 AM, Garrett Smith dhtmlkitc...@gmail.com wrote:
On Thu, Feb 28, 2008 at 10:31 AM, h...@nczonline.net wrote:
We then, as developers, could use that attribute as we see fit and
the document would still validate (for people who care about such
things).
Are people
On Mon, Dec 15, 2008 at 6:32 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Sat, Dec 13, 2008 at 1:40 AM, Garrett Smith dhtmlkitc...@gmail.com
wrote:
On Thu, Feb 28, 2008 at 10:31 AM, h...@nczonline.net wrote:
We then, as developers, could use that attribute as we see fit and
the
You're not Nicholas. We don't know if that is what Nicholas expects
his HTML to do or if he is expecting something else. In absence of an
example, I can't do much more than guess. I cannot expect your
assumptions to be correct.
Well, of course, but you sent the message to the entire group, so
Edward Z. Yang wrote:
The reason I'd like to know this is because I am the author of a tool
named HTML Purifier, which takes user-input HTML and cleans it for
standards-compliance as well as XSS. We insist on output being standards
compliant, because the result is unambiguous.
Nothing in
Geoffrey Sneddon wrote:
If you do start work on a PHP implementation, please do seriously
consider adding it to the html5lib project (which currently contains
Python and Ruby implementations) as MIT licensed — there are also a fair
number of test cases there.
I'd be quite interested in
Ian Hickson wrote:
In general you should be able to just implement what the spec says and
then either leave the HTML5 support in (it's unlikely to cause any harm)
or just comment out the support for the new elements, that should be
relatively easy.
Right, this is mostly what I intended to
James Graham wrote:
Nothing in section 8 is going to ensure that you get output that passes
a conformance check. If you do transform the output into something that
is conforming then you have to make up the rules yourself
Yes, which I suppose is slightly concerning. My philosophy is to first
On Mon, 15 Dec 2008, Edward Z. Yang wrote:
Ian Hickson wrote:
In general you should be able to just implement what the spec says and
then either leave the HTML5 support in (it's unlikely to cause any harm)
or just comment out the support for the new elements, that should be
relatively
Ian Hickson wrote:
I don't really see why a sanitiser needs extensibility though. Could you
elaborate on this? Surely you just want to filter anything that isn't
valid or safe, and only leave the valid safe stuff, using a whitelist.
In theory, I could write separate sanitizers for HTML 4,
On Mon, 15 Dec 2008, Edward Z. Yang wrote:
In theory, I could write separate sanitizers for HTML 4, XHTML 1.0,
XHTML 2.0, HTML 5, etc. In practice, I want to reuse as much code as
possible between these cases, since I'm a lazy developer. Perhaps
extensibility is not the right word here;
Ian Hickson wrote:
Oh well that's just a matter of having pluggable modules for different
things to filter. You can equally support SVG and MathML in this way. You
just need the core processing to be made independent of the filtering.
I just realized an error in my thought that I would need
On Mon, 15 Dec 2008, Edward Z. Yang wrote:
I wouldn't really worry about 4 vs 5. What matters is what works
in browsers, or whatever tools your users are using. (This is one
reason in HTML5 we do away with having the version number in the
DOCTYPE.) I'd recommend just using the HTML5
Ian Hickson wrote:
I'm not saying don't be standards-compliant; I'm just saying use a subset
of HTML5 that you feel comfortable with (which might also be a subset of
HTML4, for that matter, just with the HTML5 DOCTYPE so that you don't have
to worry about exactly which version you want to
On Mon, Dec 15, 2008 at 3:32 PM, Edward Z. Yang
edwardzy...@thewritingpot.com wrote:
Ian Hickson wrote:
I'm not saying don't be standards-compliant; I'm just saying use a subset
of HTML5 that you feel comfortable with (which might also be a subset of
HTML4, for that matter, just with the HTML5
I'm sorry to bring this up if the subject has been touched on before...
In perusing the HTML5 standard, I noticed that footnotes are still a
redheaded stepchild in the draft. Given how many workarounds and
hacks are performed to create support for footnotes using standard
elements, is
On Mon, 15 Dec 2008, Douglas Mayle wrote:
I'm sorry to bring this up if the subject has been touched on before...
In perusing the HTML5 standard, I noticed that footnotes are still a
redheaded stepchild in the draft. Given how many workarounds and hacks
are performed to create support
From my point of view (working with wikis, and more specifically with
the Xinha WYSIWYG editor) it's a use case I often run into for user-
editable content. Right now, we do all sorts of lovely things to try
and keep our magic in place (backlinks, numbering, classes, etc.).
It would be
On Mon, Dec 15, 2008 at 4:18 PM, Brenton Strine
brenton.str...@citrix.com wrote:
Maybe after having a few months to think about it some better ideas will pop
up?
I'd like to see a dedicated way to do footnotes as well. I think it would be
worth having the discussion again.
Well, as far as
Edward Z. Yang:
Sounds good, since HTML4 is a strict subset of HTML5 (correct me if I'm
wrong?)
Ian Hickson:
Mostly, yes. (There are exceptions, but they're not things you'd really
want to be using anyway, e.g. obscure SGML features.)
Note though that it’s not possible to write a
Also sprach Douglas Mayle:
As an aside tongue in cheek/ I noticed the new aside element. Isn't
aside more of a presentational decision? What's the difference
between sidenotes and footnotes other than styling? Would we be
better off combining both use cases into a single element
On Mon, 15 Dec 2008, Brenton Strine wrote:
Maybe after having a few months to think about it some better ideas will
pop up?
I'd like to see a dedicated way to do footnotes as well. I think it
would be worth having the discussion again.
If anyone has any proposals that address the issues
On Tue, 11 Nov 2008, Alexey Proskuryakov wrote:
Currently, HTML5 specifies that when a Document is discarded, close
event should be asynchronously dispatched to MessagePorts that are
entangled with ports belonging (in some specific sense) to this
document.
There is a race with garbage
On Tue, 11 Nov 2008, Jonas Sicking wrote:
The workers examples use 'event.message' in a bunch of places, however
the property is called 'event.data'.
It seems this was fixed.
Same mistake in the View this example online pages.
Yeah the files are just embedded into the spec on the fly when
On Thu, 13 Nov 2008, Jonas Sicking wrote:
It is currently possible (I think) to send a port through postMessage
after the port was started. This makes sending ports across processes
(such as to an iframe or worker living in a different process) pretty
painful to implement. It also makes
On Mon, Dec 15, 2008 at 8:02 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
You're not Nicholas. We don't know if that is what Nicholas expects
his HTML to do or if he is expecting something else. In absence of an
example, I can't do much more than guess. I cannot expect your
assumptions to be
On Mon, Dec 15, 2008 at 6:36 PM, Garrett Smith dhtmlkitc...@gmail.com wrote:
On Mon, Dec 15, 2008 at 8:02 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Valid HTML can have a clear and expected outcome. If something is done
according to standard, it can be expected that that something will
On Mon, 17 Nov 2008, Jonas Sicking wrote:
Ben just wrote up a patch to support JSON objects as well as primitive
values (0, null, false, etc) to be passed to and from workers using
postMessage.
Ok well I guess waiting for the rest to be implemented isn't going to work
if y'all start
On Tue, 18 Nov 2008, Alexey Proskuryakov wrote:
[...] If you implement the actual IPC using, say, a Unix socket, then
you can just pass the actual socket along and do the same thing
without blocking.
This is an interesting point. I do not know enough about how Unix domain
sockets are
On Tue, 18 Nov 2008, Dmitry Titov wrote:
Pages communicate with their workers (dedicated) via queue of
events.
What happens if the queue gets more and more events queued (as a result
of postMessage or timer callbacks) and the worker thread does not
consume them fast enough?
-
On Mon, 24 Nov 2008, Alexey Proskuryakov wrote:
1) The algorithm assumes that a WorkerGlobalScope exists, and doesn't
specify what happens if it is invoked before WorkerGlobalScope is
created (e.g. if the script is still being loaded, or the scope is being
created, but Worker.terminate()
Dec 16, 2008, в 9:43 AM, Ian Hickson написал(а):
1) The algorithm assumes that a WorkerGlobalScope exists, and doesn't
specify what happens if it is invoked before WorkerGlobalScope is
created (e.g. if the script is still being loaded, or the scope is
being
created, but Worker.terminate()
31 matches
Mail list logo
