Open
Bug 102952
Opened 23 years ago
Updated 12 years ago
[RFE] Validate {HTML|CSS|Links} should be available in the browser
Categories
(SeaMonkey :: UI Design, enhancement)
Tracking
(Not tracked)
NEW
Future
People
(Reporter: henrik, Assigned: bugzilla)
References
Details
(Keywords: meta)
Attachments
(1 file)
4.21 KB,
patch
|
Details | Diff | Splinter Review |
The composer part of mozilla has a nice feature where you in the "edit" menu can
choose "validate Html" and it will try to load that page into w3c's validator.
This menu item should also be avaliable in the browser part of mozilla, so the
user/ web developer can easily verify a pages html correctness
Comment 1•23 years ago
|
||
Assignee | ||
Updated•23 years ago
|
Target Milestone: --- → Future
Comment 2•23 years ago
|
||
This is very easy to do. In fact I just did it before looking for the bug :)
I just have to figure out how to get it into the tasks menu. I believe I can
also merge this code the translate code and possibly a css validator to all use
the same function.
If it's a file:// url I currently just send it to the www page and let it handle
that. In the composer one it actually sends you to the upload the file to the
validator page, but I'm not sure I can do that nicely and support translate and
CSS validation in the same function.
Comment 3•23 years ago
|
||
Comment 4•23 years ago
|
||
I can't make the entire patch with patch maker but in order for the three
commands to work these prefs have to be added to defaults\pref\all.js right
below the Translation service preferences.
// Validation service
pref("browser.validate.html.service",
"http://validator.w3.org/check?charset=%28detect+automatically%29&doctype=Inline&uri=");
pref("browser.validate.html.serviceUpload",
"http://validator.w3.org/file-upload.html");
pref("browser.validate.css.service",
"http://jigsaw.w3.org/css-validator/validator?warning=1&profile=css2&uri=");
pref("browser.validate.css.serviceUpload",
"http://jigsaw.w3.org/css-validator/validator-upload.html");
pref("browser.validate.links.service",
"http://validator.w3.org/checklink?depth=&submit=Check&uri=");
Comment 5•23 years ago
|
||
Does anyone know why this code doesn't work when the xul cache is enabled? It
appears to work fine if the cache is disabled, but as soon as I enable it, the
javascript console reports that the function which it uses does not exist.
Does navigator.js not load for navigatorOverlay.xul?
Comment 6•23 years ago
|
||
I have not tried out your patch, but it looks as if it removes the
View/Translate feature (though parts remain in navigator.dtd)
Why? Couldn't you just have added this feature in addition to Translate?
Comment 7•23 years ago
|
||
The translate button works the exact same way as these buttons. It calls a
remote cgi script with a url as one of it's paramaters.
I just converted the function which translates to be a general purpose function.
Now depending on the pref used, that same function can
translate/validate/or call any other cgi script on the web.
For example it could be modified to call
http://web.lfw.org/jminc/Malkovich/http://www.mozilla.org/
Comment 8•23 years ago
|
||
*** Bug 112501 has been marked as a duplicate of this bug. ***
Updated•23 years ago
|
Summary: Validate HTML should be avaliable in the browser part → [RFE] Validate HTML should be available in the browser
Assignee | ||
Comment 9•23 years ago
|
||
Sorry, I think this is too much of a geek feature to find its way in what should
be a mainstream browser.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 10•23 years ago
|
||
I will re-open this request on three accounts:
* Opera has a similar feature, and it doesn't appear especially geek-ish
* The feature is "allready there" in the composer.
* I thought "Netscape" was the mainstream browser, and mozilla for the developers ?
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Assignee | ||
Comment 11•23 years ago
|
||
* Opera is totally a geek browser. Look at its UI.
* It is acceptable in Composer because Composer is largely geared toward web
page designers, a more technical audience. They would certainly want to
validate their html. Users are not expected to validate the pages they view
frequently, nor would they even know what that means.
* No, Mozilla is a base browser that in theory is geared to the lowest common
denominator. Distributors take Mozilla and customize it further to suit their
end-user audience.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → WONTFIX
Comment 12•23 years ago
|
||
If you really want a Validate HTML menu item, simply create a bookmark pointing to:
javascript:void(location.href='http://validator.w3.org/check?uri='+location.href+'&ss')
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
![]() |
||
Updated•12 years ago
|
![]() |
||
Updated•12 years ago
|
Status: REOPENED → NEW
You need to log in
before you can comment on or make changes to this bug.
Description
•