Re: Element and Node are second class citizens in IE land
- From: Henry <rcornford@xxxxxxxxxxxxxx>
- Date: Tue, 15 Jul 2008 03:40:56 -0700 (PDT)
On Jul 15, 4:10 am, webbugtr...@xxxxxxxxx wrote:
My school of programming says you should not put up barriers where none
are needed, you just disempower programmers and power users.
Aaron
Agreed,
This bug (and the corresponding bug in IE Feedback can be tracked
here:http://webbugtrack.blogspot.com/2007/08/bug-186-cant-prototype-on-htmlelements.html
A bug would be a discrepancy between actual behaviour and required
behaviour. As there is no requirement that DOM interface prototypes be
exposed their not being exposed cannot be a bug. Correcting a
discrepancy between actual behaviour and desired behaviour would be an
enhancement.
Incidentally, the "bug" report is not particularly accurate as it
asserts that there are no workarounds, while there are many.
(Including, but not restricted to, Prototypes.js' strategy of using a
single function to retrieve all elements and having that function
directly modify the elements it retrieves).
.
- References:
- Element and Node are second class citizens in IE land
- From: Aaron Gray
- Re: Element and Node are second class citizens in IE land
- From: Richard Cornford
- Re: Element and Node are second class citizens in IE land
- From: Aaron Gray
- Re: Element and Node are second class citizens in IE land
- From: webbugtrack
- Element and Node are second class citizens in IE land
- Prev by Date: Re: changing multiple classnames
- Next by Date: Re: executing javascript set with innerHTML in IE 7
- Previous by thread: Re: Element and Node are second class citizens in IE land
- Next by thread: Re: Element and Node are second class citizens in IE land
- Index(es):
Relevant Pages
|
