As there is no compiler involved, these "warnings" are generated by
and other things. They are more annoying than helpful if you know
what you're doing.
Mind you, these warnings are purely out of the imagination of the
developers of one particular browser, and if you get rid of these
warnings, suddenly other warnings could pop up in the next browser
Here's an article about it:
internet down with it, so no need to have headaches over that... :)
Am 20.01.2007 um 09:56 schrieb Richard Quadling:
> Would a patch to remove the notices be acceptable to the developers?
> As a developer of commercial software for nearly 20 years and only
> recently coming to web development, I am still learning about what
> different rules apply. One of the things I've always thought is that
> if my code produces any sort of warnings now, there is always the
> chance that in years to come those warnings could become errors. If
> the compiler/interpreter is producing a warning, then I should code it
> to remove the possibility of ambiguity. Whilst the code works fine,
> removing these notices can only be a good thing.
> I don't want to turn off the notices as my own code sometimes has them
> and I go "Doh! Duh!" and fit it. It would remove the noise and help
> other developers who may not be as efficiently experienced and who do
> make the sort of mistakes that these notices are highlighting.
> On 19/01/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote:
>> Sorry, read the ill-formed sentence above as "Prototype framework
>> is coded
> Richard Quadling
> Zend Certified Engineer : http://zend.com/zce.php?
> "Standing on the shoulders of some very clever giants!"
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at