Just added (TM) to a bunch of XUL pages. hope nobody minds. These two pages need to be updated to clear up confusion about XUL knock offs. http://www.mozilla.org/projects/xul/joy-of-xul.html http://www.mozilla.org/projects/xul/ As always, volunteer wanted.
Revamping "why XUL" type documents is high on my To Do list. Don't let that stop anyone else taking it on though because I might not get aroound to iit anytime soon.
Is XUL a W3C recognized language? More than trademarking it, getting it to be a recognized standard for web UI would have a greater impact. It might encourage Opera for example to support it as well as other Mozilla supporters like IBM and SUN. Does anyboyd know which is the path to follow?
these people are in violation of our trademarks and we're going to make them stop.
Bart: Who are "these people"? XULPlanet? I kind of like them ;-)
Thanks for the linkage. I'm on the list, but my HD crashed, and mozilla mail isn't my client for a few days (slow webmail is), hence I'm very behind.
This would indeed be nice I guess.
I don't think mentioning the specific knock-offs is helpful; adding (tm) to XUL (is it indeed a trademark?) does not help clear up the confusion and is something I'd like to avoid.
Assignee: endico → nobody
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
QA Contact: imajes → doc-request
Is this a real issue we seriously need to worry about? I'm inclined to think it's not, really. I'm going to close this bug; if you think this needs revisiting, please re-open it and give your argument. But since nobody's done anything with this in a year, I don't expect much argument.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
Resolution: WORKSFORME → WONTFIX
Component: Documentation Requests → Documentation
Product: Mozilla Developer Network → Mozilla Developer Network
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.