Simon Pieters wrote:
I don't see any need for it to be case-sensitive for XHTML5. :-)
Correct me if this is incorrect but as far as I can see, according to
the specs authors have been using, id and name are case-sensitive in
XHTML 1.x just as in HTML 4.01.
Since HTML5 handles standard
On Aug 10, 2007, at 2:20 AM, Anne van Kesteren wrote:
Wouldn't it make sense to dispatch the event whenever location.hash
changes value? When following a link for instance? (Unless I
misunderstood something it's currently only dispatched in history
traversal.)
I agree with Anne's
On Fri, 10 Aug 2007, Anne van Kesteren wrote:
Wouldn't it make sense to dispatch the event whenever location.hash
changes value? When following a link for instance? (Unless I
misunderstood something it's currently only dispatched in history
traversal.)
History traversal happens as part of
Wouldn't it make sense to dispatch the event whenever location.hash
changes value? When following a link for instance? (Unless I misunderstood
something it's currently only dispatched in history traversal.)
--
Anne van Kesteren
http://annevankesteren.nl/
http://www.opera.com/
On 8/9/07, Simon Pieters [EMAIL PROTECTED] wrote:
On Wed, 08 Aug 2007 20:21:00 +0200, Michael A. Puls II
[EMAIL PROTECTED] wrote:
Just wan to be sure:
Even though id is required, name is allowed on map. Correct?
No. name is currently not allowed (but I have suggested we change to name
On Aug 10, 2007, at 12:35 PM, Ian Hickson wrote:
...leads to something that isn't IMHO that much clearer or better than
what we have now:
onhashchanged=
The advantage of hashchanged is that it is very literal -- the
attribute
called hash changed just before the event fired.
It's not
On Fri, 10 Aug 2007, Maciej Stachowiak wrote:
Some suggestions:
onfragmentscroll (thought it might not scroll if nothing has that fragment ID)
onfragmentchanged
onfragmentload (not quite accurate but reminiscent of onload)
I kind of like onfragmentload but fragment seems to have
On 8/8/07, Garrett Smith dhtmlkitchen at gmail.com wrote:
Most libraries now are providing a way to serialize a form.
It would be useful to have:
HTMLFormElement.prototype.toJSONString
HTMLFormElement.prototype.getDataSetString
HTMLFormElement.prototype.toJSONString would
On 8/10/07, Benjamin Hawkes-Lewis [EMAIL PROTECTED] wrote:
Simon Pieters wrote:
I don't see any need for it to be case-sensitive for XHTML5. :-)
Correct me if this is incorrect but as far as I can see, according to
the specs authors have been using, id and name are case-sensitive in
XHTML
