Is there a way we can make these consistent somehow? Maybe move
document.documentURI to Web Applications 1.0? With createHTMLDocument() I
get these results:
document.URL document.documentURI
Gecko about:blankabout:blank
Chrome null
Opera script
On Mon, 27 Jun 2011 07:53:53 +0200, John Giannandrea jgi...@google.com
wrote:
In the user feedback from the schema.org proposal, which uses microdata
as
its syntax, we have seen several use cases that would seem to require
multiple itemtypes per itemscope.
Currently the microdata spec only
Dnia 08-06-2011 o 21:51:57 Ian Hickson i...@hixie.ch napisał(a):
The goal of itemref= was just to have a way to handle cases where you
have an item's properties scattered around a document.
It's caused us more difficulties than helped anything, as far as I can
tell. Has anyone implemented it
On Sun, Jun 26, 2011 at 10:53 PM, John Giannandrea jgi...@google.com wrote:
In the user feedback from the schema.org proposal, which uses microdata as
its syntax, we have seen several use cases that would seem to require
multiple itemtypes per itemscope.
Could you elaborate on the use-cases
On Fri, Jun 17, 2011 at 1:40 PM, Aryeh Gregor aryehgre...@gmail.com wrote:
However, I'd still like to normalize author-set selections somewhat.
At a minimum, for instance, we could guarantee that a selection's
boundary point is always in a Text or Element node that descends from
a Document.
On Tue, 28 Jun 2011, Philip Jägenstedt wrote:
On Mon, 27 Jun 2011 07:53:53 +0200, John Giannandrea jgi...@google.com
wrote:
In the user feedback from the schema.org proposal, which uses
microdata as its syntax, we have seen several use cases that would
seem to require multiple
On Sun, Jun 26, 2011 at 5:18 PM, Robert O'Callahan rob...@ocallahan.org wrote:
Gradients already aren't continuous where the start and end points are
equal. I think it would be OK to draw nothing as Aryeh suggests. At least
it's easy to spec and implement, and I doubt authors will care (they
Ian Hickson i...@hixie.ch wrote:
The solution John proposed would indeed not handle cross-origin
extensions, which could be problematic.
Cross-origin extensions can still be handled with full URIs for the
extension properties.
I dont see how you can solve the itemtype=foo collision case for
On Tue, 28 Jun 2011, Lin Clark wrote:
On Tue, Jun 28, 2011 at 6:53 PM, Ian Hickson i...@hixie.ch wrote:
div itemscope itemtype=http://example.com/;
meta itemprop=kind content=A B
...
/div
Would it make sense to use something like vocab here?
div itemscope
Itemtype in my example is like 'kind' in your example. You are right, it is
basically a privileged property.
Because the words type and kind are pretty synonymous (groups of things that
have common characteristics), I would think that specifying an itemtype and
then specifying a separate kind
On Wed, Jun 29, 2011 at 6:19 AM, Tab Atkins Jr. jackalm...@gmail.comwrote:
On Sun, Jun 26, 2011 at 5:18 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
Gradients already aren't continuous where the start and end points are
equal. I think it would be OK to draw nothing as Aryeh suggests.
I'm happy to change WebKit to match Gecko in this regard.
Adam
On Tue, Jun 28, 2011 at 2:07 AM, Anne van Kesteren ann...@opera.com wrote:
Is there a way we can make these consistent somehow? Maybe move
document.documentURI to Web Applications 1.0? With createHTMLDocument() I
get these
My two cents, take it or leave it:
These specs and implementations are still quite immature and it's fine
to change their meaning slightly. So many things keep
breaking/changing anyway in the world of editing in practice anyway,
that there's not much point pretending to maintain backwards
13 matches
Mail list logo
