Hi.
I've wondered for some time if it weren't possible to harmonize stack
traces across browsers.
* What is the problem you are trying to solve? *
If you want a traceback, you need to cater for multiple browsers
behaviours, and different and incomplete information.
* What is the feature you
The ability to extract stack trace information from an exception is a script
language feature; it has nothing to do with HTML.
Chris
Jordan Osete wrote:
Hi.
I've wondered for some time if it weren't possible to harmonize stack
traces across browsers.
...
Personally, I don't feel like this sort of functionality belongs in an
HTML spec, but more in a JavaScript spec.
I posted a message to the es-discuss list this week
Apologies for the poor threading, I wasn't subscribed when the message
here was sent.
In http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-June/020237.html
Chris DiBona wrote:
The incredibly sucky outcome is that Chrome ships patent-encumbered
open web features, just like Apple. That
On Mon, 1 Jun 2009, Boris Zbarsky wrote:
I still think that we need a better I have some externally-derived
pixel data I'd like to just stick in this canvas API here. fillRect()
has terrible performance characteristics (as has been brought up many
times before), and the current imagedata
Ian Hickson wrote:
2) The description of putImageData says it Paints the data from the
given ImageData object onto the canvas. It may be worth
specifying that this uses the SOURCE operator, though this is
clear later on when defining what the method _really_ does.
That's the
Ian Hickson wrote:
On Mon, 1 Jun 2009, Boris Zbarsky wrote:
I still think that we need a better I have some externally-derived
pixel data I'd like to just stick in this canvas API here. fillRect()
has terrible performance characteristics (as has been brought up many
times before), and the
On Tue, 2 Jun 2009, Simon Pieters wrote:
On Tue, 02 Jun 2009 19:36:25 +0200, Jonas Sicking jo...@sicking.cc wrote:
Is this something that's really needed for web compatibility though?
Probably not.
Creating a DOM with multiple bodys is hard since the parser will
never output such a
On Wed, 3 Jun 2009, Brett Zamir wrote:
Regardless of any decision on whether my recommendation for
document.contentType to be standardized and made settable on a document
created by createDocument() (rather than needing to call the
less-than-intuitive doc.open() fix for HTML), I'd still
On Wed, 3 Jun 2009, Jeremy Orlow wrote:
When in private browsing mode, WebKit should not write any data to the
hard drive. In addition, WebKit does not allow changes to localStorage
that aren't going to be written to disk. Currently, it returns a
DOM_QUOTA_ERROR on setItem when private
On Thu, 4 Jun 2009, Brett Zamir wrote:
On Mon, 13 Apr 2009, Markus Ernst wrote:
I found a message in the list archives from July 2004, where Ian
announced to put nested optgroups back into the spec:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2004-July/001200.html
On Wed, 3 Jun 2009, Andrew W. Hagen wrote:
In current-work, section 4.6.6, there is this explanation of the small
element:
Small print is typically legalese describing disclaimers, caveats,
legal restrictions, or copyrights. Small print is also sometimes used
for attribution.
This
On Thu, 4 Jun 2009, Jonas Sicking wrote:
On Wed, Jun 3, 2009 at 3:52 PM, Ian Hickson i...@hixie.ch wrote:
I agree, keygen seems like a poor design. That's one of the reasons
I didn't extend it in HTML5; we're just defining what it does in
browsers so that new browsers can implement it
13 matches
Mail list logo
