On Mon, 12 Sep 2011 13:19:56 +0200, Simon Pieters sim...@opera.com wrote:
If you have any test cases demonstrating where Opera doesn't follow the
spec, that would be helpful in getting it fixed.
Sorry I must have glossed over this part of your email:
What about javascript: URLs?
Right now, every browser seems to treat javascript:alert('#') in an
intuitive manner.
This likely goes beyond data: and javascript:, so I think it would be
useful to look at it more holistically.
/mz
On 2011-09-12 21:47, Michal Zalewski wrote:
What about javascript: URLs?
Right now, every browser seems to treat javascript:alert('#') in an
intuitive manner.
This likely goes beyond data: and javascript:, so I think it would be
useful to look at it more holistically.
Maybe. Or it makes
On 11-09-11 10:00 PM, Ryosuke Niwa wrote:
On Tue, Aug 30, 2011 at 12:15 PM, Ryosuke Niwarn...@webkit.org wrote:
4. Jonas requested that we have manualTransact and managedTransact instead
of single transact on undoManager for clarity. I think this is a good idea
but I'd rather settle the
* Michal Zalewski wrote:
What about javascript: URLs?
Right now, every browser seems to treat javascript:alert('#') in an
intuitive manner.
With javascript:p style=margin-bottom:2000px...p id='xquot'#x
Firefox will scroll down to the second p element with value #x. That
is neither very
[ Julian Reschke ]
Observation: javascript: IMHO isn't a URI scheme (it just occupies a place
in the same lexical space), so maybe the right thing to do is to document it
as historic exception that only exists in browsers.
In one of its modes, it's roughly equivalent to data:
On Mon, Sep 12, 2011 at 1:31 PM, Ehsan Akhgari eh...@mozilla.com wrote:
On 11-09-11 10:00 PM, Ryosuke Niwa wrote:
On Tue, Aug 30, 2011 at 12:15 PM, Ryosuke Niwarn...@webkit.org wrote:
4. Jonas requested that we have manualTransact and managedTransact
instead
of single transact on
On Sat, Sep 10, 2011 at 7:01 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Tue, Aug 30, 2011 at 7:22 PM, Jonas Sicking jo...@sicking.cc wrote:
I'm really failing to think of a case when you'd really want to have
apply and reapply as separate callbacks. Even in the most trivial
cases it seems
On Mon, Sep 12, 2011 at 5:19 PM, Jonas Sicking jo...@sicking.cc wrote:
Could you please supply an example where the apply/reapply split leads
to cleaner or otherwise better code than using a boolean argument?
apply: function() {
// modify dom
// send data back to server
},
unapply:
