On Sun, Nov 1, 2009 at 3:53 AM, Darin Fisher da...@chromium.org wrote:
On Fri, Oct 30, 2009 at 1:36 AM, Robert O'Callahan
rob...@ocallahan.orgwrote:
On Fri, Oct 30, 2009 at 7:27 PM, Darin Fisher da...@chromium.org wrote:
You are right that the conditions are specific, but I don't know
I'm in perfect agreement regarding the rational behind having a model tag as
I agree with having more semantic tags in HTML. However, I don't think a
model tag would work as described as it would provide no real extra benefits
and would just confuse document authors.
The reason I feel this is
Matt Hall wrote:
When the script data state was added to the tokenizer, the tree construction
algorithm was updated to switch the tokenizer into this state upon finding a
start tag named script while in the in head insertion mode (9.2.5.7). I see
that a corresponding change was not made to 9.5
Many blogging site like posterous has theme editor for their
blog/website. It is a xml file looks more like html. Following file
was a long file which I have edited and deleted the unnecessary
content. I think this is a non-standard way to design theme. Do we
have any standard to such requirement
On Mon, Nov 2, 2009 at 1:28 AM, Robert O'Callahan rob...@ocallahan.orgwrote:
On Sun, Nov 1, 2009 at 3:53 AM, Darin Fisher da...@chromium.org wrote:
On Fri, Oct 30, 2009 at 1:36 AM, Robert O'Callahan
rob...@ocallahan.orgwrote:
On Fri, Oct 30, 2009 at 7:27 PM, Darin Fisher
narendra sisodiya schrieb:
Many blogging site like posterous has theme editor for their
blog/website. It is a xml file looks more like html. Following file
was a long file which I have edited and deleted the unnecessary
content. I think this is a non-standard way to design theme. Do we
have any
On Mon, Nov 2, 2009 at 12:43 PM, Nikita Popov pri...@ni-po.com wrote:
narendra sisodiya schrieb:
Many blogging site like posterous has theme editor for their
blog/website. It is a xml file looks more like html. Following file
was a long file which I have edited and deleted the unnecessary
David,
Excellent perspectives, and there are certainly format decisions that have
to be made as a matter of course, just as there have been for video/.
I do not agree with two of your points:
* A static 3D rendering is equal to a 2D bitmap
* JavaScript is necessary to display 3D content
My
I have a couple of editorial changes to suggest for the spec. Is this
the right place to post them?
thanks,
Liz
Elizabeth Castro
my web site: http://www.elizabethcastro.com
my blog: http://www.pigsgourdsandwikis.com
On Mon, Nov 2, 2009 at 4:14 PM, Elizabeth Castro lcas...@cookwood.com wrote:
I have a couple of editorial changes to suggest for the spec. Is this the
right place to post them?
Yes, or simply submit them as bugs directly from the spec.
~TJ
Oops, hit 'reply' instead of 'reply to all'. Forwarding to the list now
(sorry for the duplicate, brian)
Brian,
I agree that a static 3d rendering isn't really equal to a 2d bitmap, but I
think that the distinction will be lost on most people. As to javascript not
being required? I think that
I've noticed a couple of instances in which the spec gives the content
model for a given element, like for example, the hgroup element
contains one or more of h1, h2, etc., and then specifies what should
happen even if the element doesn't contain what it's supposed to, as
here where we
The third to last word in this line:
If node has an ancestor element that is a article element
should be an
Liz
In 4.4.11, it says
Sectioning content elements are always considered subsections of
their nearest ancestor element of sectioning content, regardless of
what implied sections other headings may have created.
Does that line mean that a section element is *not* a subsection of
the nearest
David,
To respond to your points:
* I'm a bit confused as to what re-engineering you are referring. You say
layering on top of HTML at the end of your response, but none of the
example code in this thread amounts to an intrinsic change to HTML
whatsoever (it actually riffs heavily on video/),
Additional clarification on this proposal:
A model Element Never Becomes a Wafer
---
Right now, if you try to act on conventional HTML elements with 3D
CSS, those elements become wafers.
See here: http://webkit.org/blog/386/3d-transforms/
On Nov 2, 2009, at 3:41 PM, Brian Blakely wrote:
Additional clarification on this proposal:
A model Element Never Becomes a Wafer
---
Right now, if you try to act on conventional HTML elements with 3D
CSS, those elements become wafers.
On Tue, Nov 3, 2009 at 6:36 AM, Darin Fisher da...@chromium.org wrote:
1a) Given a page (domain A) containing an iframe (domain B), have the outer
page navigate the inner frame to about:blank. This navigation completes
synchronously, and the unload handler for the iframe runs before the
Simon,
* Though it does not have properties for clipping, Webkit's proposed
implementation of 3D CSS does have them for perspective. Clipping,
lighting, texture stretching and additional considerations could also
be a part of that spec, but those are discussions for the CSS WG.
Without a 3D
Spinning Cube Example
Integrating 3D Media Type with Current Techniques
---
(note: the only significant difference between this and
currently implemented technology is the media type
and additional CSS properties suited
* 2D bitmaps are only partially compatible with 3D CSS - they are still always
flat3D object will finally be present as a 2d bitmap. there are always a
process called rendering.you idea may be similar with the VRML, such as
Box(x,y,z,w,l,h) but VRML still need some ActiveX to render it into
CYp,
We are speaking about a native, semantic 3D media type. It is
inherently compatible with 3D CSS and requires no additional code to
display. This is very different from a 2D rendering based on 3D
properties (as with VRML and canvas/).
-Brian
2009/11/2 CYp tccy...@hotmail.com:
* 2D
On Mon, 2 Nov 2009, Elizabeth Castro wrote:
I have a couple of editorial changes to suggest for the spec. Is this
the right place to post them?
Yes.
If they're trivial, e.g. typos, then the easiest way is to use the submit
review comments feature at the bottom of the screen when viewing the
On Mon, 2 Nov 2009, Elizabeth Castro wrote:
I've noticed a couple of instances in which the spec gives the content
model for a given element, like for example, the hgroup element contains
one or more of h1, h2, etc., and then specifies what should happen even
if the element doesn't contain
On Nov 2, 2009, at 4:26 PM, Brian Blakely wrote:
* Though it does not have properties for clipping, Webkit's proposed
implementation of 3D CSS does have them for perspective. Clipping,
lighting, texture stretching and additional considerations could also
be a part of that spec, but those are
25 matches
Mail list logo
