- This topic has 5 replies, 3 voices, and was last updated 17 years, 11 months ago by Greg.
-
AuthorPosts
-
Rod BollingerMemberHello,
In MyEclipse 5.1.0GA, the HTML Editor has tabs for IE Preview and Mozilla Preview. When using these tabs MyEclipse does not recognize the xmlns attribute of the <html> tag (e.g. <html xmlns=”http://www.w3.org/1999/xhtml”>). Everything from xmlns through the end of the attribute is shown in plain text at the top of the page in preview mode.
Also, and possibly a reason for the above behavior, when editing the (x)html source code the xmlns attribute is not available in code assist. In other words, it would appear that this attribute is unknown to MyEclipse.
My understanding was that MyEclipse supported XHTML. Am I missing something, or is this a known bug?
[Environment] Eclipse 3.2.1, MyEclipse 5.1.0GA, WinXP Pro
Thanks,
-Rod
Riyad KallaMemberRod,
As I mentioned in your other post full XHTML isn’t in MyEclipse just yet. It is something we are evaluating for the 6.0 release. Sorry for the confusion.
GregMemberRod,
Could you post a small xhtml example that demonstrates this issue? This shouldn’t be happening, so maybe we can fix this particular issue even though we may not have full xhtml support.
Rod BollingerMemberHi Greg,
Sure, here is the smallest valid snippet of XHTML possible and it will exhibit the problem in bothe IE and Mozilla Preview views:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Test XHTML Template</title> </head> <body> </body> </html>
[Environment] Eclipse 3.2.1 / MyEclipse 5.1.0GA / JDK 1.5.0_08 / WinXP Pro
I appreciate you taking a second look.
Thanks,
-Rod
Rod BollingerMemberHi Greg,
I was wondering if you had a chance to verify the listed behavior and whether or not you found the reason?
Thanks,
-Rod
GregMemberRod,
Sorry for taking so long to get back around to answering you. Yes, we were able to replicate your issue. I filed a PR and attached this support thread to it. Hopefully our developers can have a look and try to get a fix in for the next release. Thanks for the report and sorry for the inconvenience.
-
AuthorPosts