, 2012 7:39 PM
To: Adam Barth aba...@webkit.org, Andrei Bucur abu...@adobe.com
Cc: webkit-dev@lists.webkit.org webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Web APIs and class name collisions
The spec itself consistently and deliberately calls them CSS
Regions,
so a
CSS
@lists.webkit.org
Subject: Re: [webkit-dev] Web APIs and class name collisions
One common thing we do is prefix DOM to DOM-level concepts. For
example,
DOMWindow and DOMFileSystem. I'm not sure if we have an established
convention for CSS-level concepts.
Adam
On Thu, Jul 12, 2012 at 9
Date: Thursday, July 12, 2012 7:39 PM
To: Adam Barth aba...@webkit.org, Andrei Bucur abu...@adobe.com
Cc: webkit-dev@lists.webkit.org webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Web APIs and class name collisions
The spec itself consistently and deliberately calls them
Hello Webkittens!
While implementing the Region interface (
http://dev.w3.org/csswg/css3-regions/#the-region-interface ) I've noticed that
the name Region is already taken by a class in platform/graphics. I'd like to
know what's the best approach in these kind of situations:
1. Rename the
One common thing we do is prefix DOM to DOM-level concepts. For example,
DOMWindow and DOMFileSystem. I'm not sure if we have an established
convention for CSS-level concepts.
Adam
On Thu, Jul 12, 2012 at 9:18 AM, Andrei Bucur abu...@adobe.com wrote:
Hello Webkittens!
While implementing
@lists.webkit.org
webkit-dev@lists.webkit.orgmailto:webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Web APIs and class name collisions
One common thing we do is prefix DOM to DOM-level concepts. For example,
DOMWindow and DOMFileSystem. I'm not sure if we have an established convention
for CSS
...@webkit.orgmailto:aba...@webkit.org, Andrei Bucur
abu...@adobe.commailto:abu...@adobe.com
Cc: webkit-dev@lists.webkit.orgmailto:webkit-dev@lists.webkit.org
webkit-dev@lists.webkit.orgmailto:webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Web APIs and class name collisions
The spec itself consistently
: Thursday, July 12, 2012 7:39 PM
To: Adam Barth aba...@webkit.org, Andrei Bucur abu...@adobe.com
Cc: webkit-dev@lists.webkit.org webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Web APIs and class name collisions
The spec itself consistently and deliberately calls them CSS Regions,
so
Subject: Re: [webkit-dev] Web APIs and class name collisions
The spec itself consistently and deliberately calls them CSS Regions,
so a
CSS prefix could be appropriate.
Thanks,
Alan
From: Adam Barth aba...@webkit.org
To: Andrei Bucur abu...@adobe.com
Cc: webkit-dev
,
Andrei.
From: Alan Stearns stea...@adobe.com
Date: Thursday, July 12, 2012 7:39 PM
To: Adam Barth aba...@webkit.org, Andrei Bucur abu...@adobe.com
Cc: webkit-dev@lists.webkit.org webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Web APIs and class name collisions
The spec itself
,
Andrei.
From: Alan Stearns stea...@adobe.com
Date: Thursday, July 12, 2012 7:39 PM
To: Adam Barth aba...@webkit.org, Andrei Bucur abu...@adobe.com
Cc: webkit-dev@lists.webkit.org webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Web APIs and class name collisions
The spec itself
@lists.webkit.org
Subject: Re: [webkit-dev] Web APIs and class name collisions
One common thing we do is prefix DOM to DOM-level concepts. For
example,
DOMWindow and DOMFileSystem. I'm not sure if we have an established
convention for CSS-level concepts.
Adam
On Thu, Jul 12, 2012 at 9
To: Adam Barth aba...@webkit.org, Andrei Bucur abu...@adobe.com
Cc: webkit-dev@lists.webkit.org webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Web APIs and class name collisions
The spec itself consistently and deliberately calls them CSS Regions,
so a
CSS prefix could
13 matches
Mail list logo