Control over HTML errors? Follow

Colin Fleming wrote:

Is there any? They don't seem to appear in the config/errors panel.
One I would dearly love to turn off is "image lacks alt attribute" -
I'm not even sure if this is mandated by the spec or if it's just a
best practice, but I'm working on a totally internal application that
will never be used by blind people, and there's no way I can go
change all the img tags.

Sorry, you're writing invalid XML, or if it's HTML, you're writing
invalid HTML. The JIRA bug report for this was marked "Won't fix"

Hi,

There will be ability to suppress html warnings for undeclared
tags/attributes/missed parameters
(http://www.jetbrains.net/jira/browse/IDEADEV-1208)


Keith Lea wrote:

Colin Fleming wrote:

>> Is there any? They don't seem to appear in the config/errors panel.
>> One I would dearly love to turn off is "image lacks alt attribute" -
>> I'm not even sure if this is mandated by the spec or if it's just a
>> best practice, but I'm working on a totally internal application that
>> will never be used by blind people, and there's no way I can go
>> change all the img tags.
>>

Sorry, you're writing invalid XML, or if it's HTML, you're writing
invalid HTML. The JIRA bug report for this was marked "Won't fix"

--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

Now, I understand this attitude towards XML files. If IDEA catches a problem with a XML file, chances are the file simply won't work -- the parser will choke.

When it comes to HTML, things are not that set in stone. You would be surprised by the garbage browsers correctly parse and render. IDEA shouldn't be be pointing something as an error without any option to turn it off when the file will still work perfectly with that "error".

+aleph(1)

See the "JSP and HTML/JavaScript do not play together" discussion.

When it comes to HTML, things are not that set in
stone. You would be surprised by the garbage browsers
correctly parse and render. IDEA shouldn't be be
pointing something as an error without any option to
turn it off when the file will still work perfectly
with that "error".

Exactly. When I'm writing new code, it's always compliant. But when I'm maintaining old code (especially for an internal project like this one) I can't just go round adding alt tags when realistically they won't be used for anything.

Marcus Brito wrote:

When it comes to HTML, things are not that set in stone. You would be
surprised by the garbage browsers correctly parse and render. IDEA
shouldn't be be pointing something as an error without any option to
turn it off when the file will still work perfectly with that
"error".

Just cause browsers accept crap, the mentality of "lets just continue to
write said crap" doesn't make the world any better, it just continues to
make it suck.

Just cause browsers accept crap, the mentality of
"lets just continue to
write said crap" doesn't make the world any better,
it just continues to
make it suck.

I know, but try maintaining a 5 years old application using IDEA right now. Unless you have an unspoken love for the color red, it won't be exactly an enjoyable experience.

^^^
What he said. Right now, I'm just thankful I'm colourblind.

+10
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Marcus Brito wrote:

When it comes to HTML, things are not that set in

stone. You would be

surprised by the garbage browsers correctly parse

and render. IDEA

shouldn't be be pointing something as an error

without any option to

turn it off when the file will still work perfectly

with that

"error".

Just cause browsers accept crap, the mentality of
"lets just continue to
write said crap" doesn't make the world any better,
it just continues to
make it suck.

Hmmm. I just define alt="" and it fixes the problem. Doesn't seem a required attribute to me... Standards I suppose...

dean

1) Try defining alt="" in a few thousand locations.
2) Like "missing alt attribute" is the only problem...