On Thu, Jul 28, 2011 at 12:44 PM, Hill, Brad wrote:
> What are the use cases where a user is better off if their browser obeys
> From-Origin than if it does not?
>
> Bandwidth "theft"? The user wants to see the image. The problem, such
> that one exists, is for the hosting server. They can and
The ability to do all of these things server-side, with referrer checking, has
been universally available for fifteen years. (RFC 1945)
In every one of the use cases below, From-Origin is a worse solution than
referrer checking. What is the benefit? Why should I choose From-Origin? Why
shou
On Jul 15, 2011, at 7:51 AM, Thomas Roessler wrote:
> On Jul 15, 2011, at 16:47 , Anne van Kesteren wrote:
>
>> On Fri, 15 Jul 2011 14:43:13 +0200, Arthur Barstow
>> wrote:
>>> As indicated a year ago [1] and again at the end of last month [2], the
>>> proposal to create a new Web Application
On Jul 31, 2011, at 5:52 PM, Bjoern Hoehrmann wrote:
> * Anne van Kesteren wrote:
>> http://www.w3.org/TR/from-origin/
>
> The proposed `From-Origin` header conveys a subset of the information
> that is already available through the Referer header.
From-Origin is a response header and Referer
On Aug 1, 2011, at 10:29 AM, Hill, Brad wrote:
> The ability to do all of these things server-side, with referrer checking,
> has been universally available for fifteen years. (RFC 1945)
>
> In every one of the use cases below, From-Origin is a worse solution than
> referrer checking. What
On Tue, 17 May 2011, Paul Kinlan wrote:
>
> Consider this flow. We have a multi paged app with pages A and B when
> rendered from the server sharing the same AppCache and thus in the same
> group.
>
>- User visits page A, it uses an app cache, so everything is cached.
>- User navigates
In an IRC discussion with Ian Hickson and Tab Atkins, we can up with the
following idea for convenient element creation:
Element.create(tagName, attributeMap, children…)
Creates an element with the specified tag, attributes, and children.
tagName - tag name as a string; by default it doe
On Mon, 1 Aug 2011, Maciej Stachowiak wrote:
>
>Creates an element with the specified tag, attributes, and children.
>
>tagName - tag name as a string; by default it does "smart" selection
> of SVG, HTML or MathML namespace. Authors can also use an html: svg: or
> mathml: prefix to over
On Mon, Aug 1, 2011 at 6:33 PM, Maciej Stachowiak wrote:
>
> In an IRC discussion with Ian Hickson and Tab Atkins, we can up with the
> following idea for convenient element creation:
>
> Element.create(tagName, attributeMap, children…)
>
Can we alternatively extend document.createElement? Or wa
On Aug 1, 2011, at 6:43 PM, Ian Hickson wrote:
> On Mon, 1 Aug 2011, Maciej Stachowiak wrote:
>>
>> Creates an element with the specified tag, attributes, and children.
>>
>> tagName - tag name as a string; by default it does "smart" selection
>> of SVG, HTML or MathML namespace. Autho
On Mon, 1 Aug 2011, Ryosuke Niwa wrote:
> On Mon, Aug 1, 2011 at 6:33 PM, Maciej Stachowiak wrote:
> >
> > In an IRC discussion with Ian Hickson and Tab Atkins, we can up with
> > the following idea for convenient element creation:
> >
> > Element.create(tagName, attributeMap, children�)
>
> Can
On Mon, Aug 1, 2011 at 6:43 PM, Ian Hickson wrote:
> On Mon, 1 Aug 2011, Maciej Stachowiak wrote:
>>
>> Creates an element with the specified tag, attributes, and children.
>>
>> tagName - tag name as a string; by default it does "smart" selection
>> of SVG, HTML or MathML namespace. Authors
On , Ian Hickson wrote:
On Mon, 1 Aug 2011, Ryosuke Niwa wrote:
On Mon, Aug 1, 2011 at 6:33 PM, Maciej Stachowiak wrote:
>
> In an IRC discussion with Ian Hickson and Tab Atkins, we can up with
> the following idea for convenient element creation:
>
> Element.create(tagName, attributeMap, chi
On 2/08/11 3:36 PM, João Eiras wrote:
However, Nodes need a ownerDocument, and that needs to be supplied, even
if optionally. Doing document.createElement implies the document,
Element.create does not.
I figure the ownerDocument would be window.document (where the window
object is the global o
On Mon, Aug 1, 2011 at 7:05 PM, Charles Pritchard wrote:
> Can we have it 'inherit' a parent namespace, and have chaining properties?
>
> Element.create('div').create('svg').create('g').create('rect', {title: 'An
> svg rectangle in an HTML div'});
Ooh, so .create is defined both on Element (defa
On , Tab Atkins Jr. wrote:
On Mon, Aug 1, 2011 at 7:05 PM, Charles Pritchard wrote:
Can we have it 'inherit' a parent namespace, and have chaining properties?
Element.create('div').create('svg').create('g').create('rect', {title: 'An svg
rectangle in an HTML div'});
Ooh, so .create is def
On Mon, Aug 1, 2011 at 8:52 PM, João Eiras wrote:
> On , Tab Atkins Jr. wrote:
>
>> On Mon, Aug 1, 2011 at 7:05 PM, Charles Pritchard wrote:
>>>
>>> Can we have it 'inherit' a parent namespace, and have chaining
>>> properties?
>>>
>>> Element.create('div').create('svg').create('g').create('rect
On Tue, 2 Aug 2011, João Eiras wrote:
>
> However, Nodes need a ownerDocument, and that needs to be supplied, even
> if optionally. Doing document.createElement implies the document,
> Element.create does not.
Just use the same document as new Image(), new Option(), or new Audio().
--
Ian Hic
On Tue, 2 Aug 2011, João Eiras wrote:
>
> While the idea is interesting, "create" is a too simple name to add on
> something as polluted as Element.
Why?
I think create() is fine. It's a pretty common name for a factory or
constructor (in languages with named constructors), and having it on th
On Aug 1, 2011, at 8:36 PM, João Eiras wrote:
> On , Ian Hickson wrote:
>
>> On Mon, 1 Aug 2011, Ryosuke Niwa wrote:
>>> On Mon, Aug 1, 2011 at 6:33 PM, Maciej Stachowiak wrote:
>>> >
>>> > In an IRC discussion with Ian Hickson and Tab Atkins, we can up with
>>> > the following idea for conven
On Aug 1, 2011, at 8:43 PM, Tab Atkins Jr. wrote:
> On Mon, Aug 1, 2011 at 7:05 PM, Charles Pritchard wrote:
>> Can we have it 'inherit' a parent namespace, and have chaining properties?
>>
>> Element.create('div').create('svg').create('g').create('rect', {title: 'An
>> svg rectangle in an HTM
On Aug 1, 2011, at 9:25 PM, Ian Hickson wrote:
> On Tue, 2 Aug 2011, João Eiras wrote:
>>
>> While the idea is interesting, "create" is a too simple name to add on
>> something as polluted as Element.
>
> Why?
>
> I think create() is fine. It's a pretty common name for a factory or
> constru
22 matches
Mail list logo
