I'm an implementer (to the fullest extent that one can be one by
modifying existing open source), just following the convention of this
list of stating my use case. The use case reflects reality since it
was implemented last year.
On Mon, Aug 31, 2015 at 12:04 PM, Domenic Denicola
On Fri, Aug 28, 2015 at 11:17 AM, Domenic Denicola wrote:
> From: Robert O'Callahan
>
>> According to the spec it should work, but it's very low priority for us and
>> implementing it would be very inefficient as Yay295 describes. So I don't
>> think it's going to happen in Firefox in the
PB,
No matter what display method you use, it sounds like an important
requirement is to keep users from ever viewing the HTML of a row other
than from your display app/page. It seems to me to achieve this you
must not use URIs alone to fetch the row view that goes in the row's
frame, because
On Mon, Jul 27, 2009 at 11:50 AM, Michael Davidsonm...@google.com wrote:
THE PROBLEM
snip
feature parity with desktop applications.
snip
A SOLUTION
snip
hidden HTML/JS page running
in the background that can access the DOM of visible windows.
snip
KNOWN ISSUES
As mentioned in
On Thu, Jul 23, 2009 at 2:48 PM, Manu Spornymspo...@digitalbazaar.com wrote:
I can git clone the Linux kernel, mess around with it and submit a patch
to any number of kernel maintainers. If that patch is rejected, I can
still share the changes with others in the community. Using the same
Is it possible that the usage of HTTP to obtain a document for rendering and
to obtain a document for XHR would differ sufficiently that the HTTP headers
would differ?
On Wed, Jul 15, 2009 at 12:07 PM, Joseph Pecoraro joepec...@gmail.comwrote:
It seems like an oversight that Javascript can read
On Fri, 17 Apr 2009, Michael Enright wrote:
If you use HTML as a text file format you can still let the receiving
parser infer all sorts of tags and allow yourself to write things like
Andersen's first HTML version. If you want a title, put a title element
in. Is the concern about validation
If you use HTML as a text file format you can still let the receiving
parser infer all sorts of tags and allow yourself to write things like
Andersen's first HTML version. If you want a title, put a title
element in. Is the concern about validation? Can one really get in
that much trouble without
On Tue, Mar 18, 2008 at 2:23 PM, Christoph Päper
[EMAIL PROTECTED] wrote:
+ h4Attributes common to codetd/code and codeth/code
elements/h4
+ pThe codetd/code and codeth/code elements may have a dfn
+ title=attr-tdth-colspancodecolspan/code/dfn content
+ attribute specified,
If this is commonly done with just one line of JS then a bot could
probably find a significant number of pages with that one-liner in the
'a' element's attributes. By one line, I mean a simple unwrapped
property change or invocation of a standard method, not through a
wrapper.
It would be worth
Although the XMLHttpRequest has the capability of making a DOM
available from the resulting text, the client and server don't have to
make use of it. One could take the responseText and pass it to eval()
if the other end sent JSON. A BEEP API should support any valid use of
BEEP, just as
11 matches
Mail list logo
