On Sat, 18 Jul 2009, Adam Barth wrote:
> On Fri, Jul 17, 2009 at 4:10 PM, Ian Hickson wrote:
> > Suppose that there is a tool where someone can write some text, in which
> > case the text will be displayed when the page is loaded. Suppose that
> > whether the person has written this text is confide
On Fri, Jul 17, 2009 at 4:10 PM, Ian Hickson wrote:
> Suppose that there is a tool where someone can write some text, in which
> case the text will be displayed when the page is loaded. Suppose that
> whether the person has written this text is confidential, and that whether
> one had entered text
On Mon, 29 Jun 2009, Ojan Vafai wrote:
> On Tue, Jun 2, 2009 at 11:38 PM, Ian Hickson wrote:
> > On Fri, 3 Apr 2009, Ojan Vafai wrote:
> > >
> > > I'm suggesting an addition to cross-domain (i)frames that allows
> > > scrolling specific content into view. The use case is sites that
> > > aggrega
On Tue, Jun 2, 2009 at 11:38 PM, Ian Hickson wrote:
> On Fri, 3 Apr 2009, Ojan Vafai wrote:
> >
> > I'm suggesting an addition to cross-domain (i)frames that allows
> > scrolling specific content into view. The use case is sites that
> > aggregate data from many sites (e.g. search engines) and wa
On Fri, 3 Apr 2009, Ojan Vafai wrote:
>
> I'm suggesting an addition to cross-domain (i)frames that allows
> scrolling specific content into view. The use case is sites that
> aggregate data from many sites (e.g. search engines) and want to display
> that data in an iframe. They can load the pag
On Tue, Apr 14, 2009 at 9:48 AM, Alex Russell wrote:
> On Thu, Apr 9, 2009 at 6:21 AM, Jon Barnett wrote:
>> On Mon, Apr 6, 2009 at 3:51 PM, Jonas Sicking wrote:
>>>
>>> >From my point of view I'm not sure how interesting this whole feature
>>> is. We had support in firefox for XPointer for many
On Thu, Apr 9, 2009 at 6:21 AM, Jon Barnett wrote:
> On Mon, Apr 6, 2009 at 3:51 PM, Jonas Sicking wrote:
>>
>> >From my point of view I'm not sure how interesting this whole feature
>> is. We had support in firefox for XPointer for many years and saw
>> little to no uptake. I'm not sure if anyon
On Apr 9, 2009, at 16:21, Jon Barnett wrote:
Do other browsers have easy scripting support for XPath?
In addition to Gecko, WebKit and Presto support the
document.evaluate() API for using XPath from JS.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
IMHO, XPath support can be programmed into a script library; the only
requirement is DOM access.
Chris
Jon Barnett wrote:
Was it advertized?
Not particularly.
I follow Firefox closely enough, but I don't remember when XPointer was
supported.
If you only follow "Firefox", then you might not have have noticed it
anyway. XPointer support for anchor scrolling was added to Gecko in
March 2003
On Mon, Apr 6, 2009 at 3:51 PM, Jonas Sicking wrote:
> >From my point of view I'm not sure how interesting this whole feature
> is. We had support in firefox for XPointer for many years and saw
> little to no uptake. I'm not sure if anyone complained when we removed
> the support even (which woul
On Mon, Apr 6, 2009 at 11:33 AM, Giovanni Campagna
wrote:
> 2009/4/6 Ojan Vafai :
>> On Fri, Apr 3, 2009 at 10:46 PM, Cameron McCormack wrote:
>>>
>>> Ojan Vafai:
>>> > 2) Add a css or xpath expression to fragment identifiers. Tthe iframe
>>> > src can be set to http://foo.com#css(.foo #bar). Sam
2009/4/6 Ojan Vafai :
> On Fri, Apr 3, 2009 at 10:46 PM, Cameron McCormack wrote:
>>
>> Ojan Vafai:
>> > 2) Add a css or xpath expression to fragment identifiers. Tthe iframe
>> > src can be set to http://foo.com#css(.foo #bar). Same as above
>> > applies. If there's no match, it's a noop. If ther
On Fri, Apr 3, 2009 at 10:46 PM, Cameron McCormack wrote:
> Ojan Vafai:
> > 2) Add a css or xpath expression to fragment identifiers. Tthe iframe
> > src can be set to http://foo.com#css(.foo #bar). Same as above
> > applies. If there's no match, it's a noop. If there is a match, it
> > scrolls t
On Sun, Apr 5, 2009 at 1:09 AM, Giorgio Maone wrote:
> It would make clickjacking attacks more precise, by exactly positioning the
> frame content where the attacker wants it to be.
> Not that you cannot already be pixel-precise by using absolute positioning
> inside an overflow: hidden div...
> L
Peter Kasting wrote, On 05/04/2009 0.54:
On Sat, Apr 4, 2009 at 12:56 PM, timeless wrote:
sounds like a security nightmare.
Can you be less vague? We've had a number of security people vet this
already, so specific complaints would be very helpful.
PK
It would make clickjacking at
On Sat, Apr 4, 2009 at 12:56 PM, timeless wrote:
> sounds like a security nightmare.
Can you be less vague? We've had a number of security people vet this
already, so specific complaints would be very helpful.
PK
sounds like a security nightmare.
we already have people complaining about reframing and spoofing and things.
Ojan Vafai:
> 2) Add a css or xpath expression to fragment identifiers. Tthe iframe
> src can be set to http://foo.com#css(.foo #bar). Same as above
> applies. If there's no match, it's a noop. If there is a match, it
> scrolls the first one into view.
Sounds like XPointer:
http://www.w3.org/TR
I'm suggesting an addition to cross-domain (i)frames that allows scrolling
specific content into view. The use case is sites that aggregate data from
many sites (e.g. search engines) and want to display that data in an iframe.
They can load the page in an iframe, but they have no way to make the
co
20 matches
Mail list logo
