Your main point is well taken.
There are some technical reasons why tag whitelisting makes more sense
for inline content. For example, consider the case you mentioned on
webkit-dev: @id. Inline, @id is problematic because the ids exist in
a per-frame namespace, whereas they're harmless when the
On Wed, 11 Nov 2009, Simon Pieters wrote:
On Wed, 11 Nov 2009 16:05:53 +0100, Simon Pieters sim...@opera.com wrote:
Shouldn't setting onmessage on a Worker object enable the port message
queue?
Currently step 8 of the run a worker algorithm enables the port
message queue for the
On Wed, 11 Nov 2009, David Bruant wrote:
This is a new proposal taking into account the feedback I recieved to
the [WebWorkers] About the delegation example message.
In the delegation example of the WebWorker spec, we can see this line :
var num_workers = 10;
My concern is about the
The WebKit community is considering taking up such an experimental
implementation. Here's my current proposal for how this might work:
http://docs.google.com/Doc?docid=0AZpchfQ5mBrEZGQ0cDh3YzRfMTJzbTY1cWJrNAhl=en
I would appreciate any feedback on the design.
Whitelist requires developers to
Philip Jägenstedt wrote:
As currently speced, the proper usage of figure is:
figure
ddimg src=bunny.jpg alt=A Bunny/dd
dtThe Cutest Animal/dt
/figure
Apart from all that has been said about legacy parsing, leaking style in
IE, etc I would (perhaps not be the first to) add:
1. It seems quite
The original idea for using the attribute was that it could apply to a
wide range of elements, like p, div, etc. But that makes it difficult
for browsers to provide sensible default styling for captions, since
it requires carefully overriding existing defaults for so many other
elements.
On Tue, Dec 1, 2009 at 7:28 AM, Lachlan Hunt lachlan.h...@lachy.id.au wrote:
To some extent, it even makes it difficult for authors to provide reasonable
styles if they can't guarantee which elements content writers will choose
for their caption. Imagine designing a CMS template with some
On Tue, 01 Dec 2009 15:33:28 +0100, Nikita Popov pri...@ni-po.com wrote:
There are only 2 sensible options for element choices: legend or
introducing a new element. Using dt/dd is *not* and was never a
sensible choice for figure, and the idea must be dropped.
As caption and legend have much
2009/12/1 Kornel Lesiński kor...@geekhood.net:
The WebKit community is considering taking up such an experimental
implementation. Here's my current proposal for how this might work:
http://docs.google.com/Doc?docid=0AZpchfQ5mBrEZGQ0cDh3YzRfMTJzbTY1cWJrNAhl=en
I would appreciate any
Tab Atkins Jr. wrote:
On Tue, Dec 1, 2009 at 7:28 AM, Lachlan Huntlachlan.h...@lachy.id.au wrote:
To some extent, it even makes it difficult for authors to provide reasonable
styles if they can't guarantee which elements content writers will choose
for their caption. Imagine designing a CMS
On Tue, Dec 1, 2009 at 9:07 AM, Lachlan Hunt lachlan.h...@lachy.id.au wrote:
Applying reset styles alone and making all elements look the same basically
defeats the purpose of being able to use a range of different elements, and
is very likely not what an author would ultimately want.
Heh, you
On 1 Dec 2009, at 14:33, Nikita Popov wrote:
As caption and legend have much too many backwards compatibility
issues
It's not bad I think. I've played a little with the live DOM viewer
and this seems usable:
figure
content
captiondiv class=captionfoo/div/caption
/figure
caption
On Tue, 01 Dec 2009 14:28:32 +0100, Lachlan Hunt
lachlan.h...@lachy.id.au wrote:
Philip Jägenstedt wrote:
As currently speced, the proper usage of figure is:
figure
ddimg src=bunny.jpg alt=A Bunny/dd
dtThe Cutest Animal/dt
/figure
Apart from all that has been said about legacy parsing,
On Tue, 01 Dec 2009 16:36:08 +0100, Philip Jägenstedt phil...@opera.com
wrote:
You only need to provide styles for the elements you're using which
wouldn't work with a simple generic style such as.
figure[caption] { margin-left: 1em; font-weight: bold; }
Please, no examples where this
And even whitelist for CSS properties couldn't be used to implement
No
external access policy (allow images with data: urls, allow http:
links,
but not http: images). This would be useful for webmails and other
places
where website doesn't want to allow 3rd parties tracking views.
I
2009/12/1 Kornel Lesiński kor...@geekhood.net:
And even whitelist for CSS properties couldn't be used to implement No
external access policy (allow images with data: urls, allow http: links,
but not http: images). This would be useful for webmails and other places
where website doesn't want to
Is there a reason we can't reuse legend (or label)? I don't think
giving p an attribute that it can only use inside of figure is
very straightforward.
On Tue, Dec 1, 2009 at 6:01 PM, Hugh Guiney hugh.gui...@gmail.com wrote:
Is there a reason we can't reuse legend (or label)? I don't think
giving p an attribute that it can only use inside of figure is
very straightforward.
Yes. legend is documented as having rendering issues in all current
On Thu, 12 Nov 2009, David Bruant wrote:
I was waiting for Firefox to stop freezing on the HTML5 spec page (it
freezes about one minute each time I visit the one-page version) and I
tried to think of a way to design this page in a way that wouldn't
freeze my browser.
The easiest way is to
On Dec 1, 2009, at 4:08 PM, Tab Atkins Jr. wrote:
On Tue, Dec 1, 2009 at 6:01 PM, Hugh Guiney hugh.gui...@gmail.com
wrote:
Is there a reason we can't reuse legend (or label)? I don't think
giving p an attribute that it can only use inside of figure is
very straightforward.
Yes. legend is
On Wed, 25 Nov 2009, Simon Pieters wrote:
The Interface objects and constructors section says
There must be no interface objects and constructors available in the
global scope of scripts whose script's global object is a
WorkerGlobalScope object except for the following:
On Thu, 26 Nov 2009, Simon Pieters wrote:
There's ErrorEvent.initErrorEvent, and dispatchEvent is exposed in
workers, but there's no createEvent (because there's no document). Are
there use cases for sending events in a worker? Should we expose
createEvent somewhere? Should we remove
22 matches
Mail list logo
