Community
Participate
Working Groups
i got an html file with the suffix .aspx (foo.aspx). default editor does not display any syntax coloring or enables completion, so i used right click -> open with -> HTML Editor but the editor still does not show any coloring nor auto completion. after simply renaming the very same file to foo.html, everything works. the editor should not force its own ideas about the file type upon me -- when i decide, i want to open it as an html file, it has to accept that and open it as an html file. -- Configuration Details -- Product: Eclipse 1.3.2.20110218-0812 (org.eclipse.epp.package.jee.product) Installed Features: org.eclipse.platform 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi
Please see http://wiki.eclipse.org/WTP_FAQ#How_do_I_use_my_own_filename_extensions_in_the_XML_editor.3F_It_only_works_correctly_if_a_file_ends_with_.xml.
i knew about that already, but that's no solution, it's not even a workaround. if i say "open this file as an html file", the editor has to do that. i can't for a single file i get add just another association, just because the editor is to stupid or stubborn to do what _i_ want. i get that file with a "could you please quickly look into it" and i need to define a new association just for that single file? you must be kidding! associations are nice for extensions i get often, but if the editor in bad old microsoft-style relies on the file extension instead of being either smart and recognize the type or at least follow a user's instructions, then it is broken. period.
The problem you've run into is an architectural limitation for which no solution currently exists. The surrounding systems in Eclipse won't acknowledge that file extension as one for HTML by default (nor should they as the set of elements with the "asp" prefix would be reported as unknown tags). A documented workaround *has* been given, but we'll continue to pursue a more streamlined version with bug 320996.
that's at least an _useful_ answer! i got to insist, though, that the given "workaround" is _not_ a workaround for the issue!
