Closed
Bug 54726
Opened 25 years ago
Closed 24 years ago
Add link to W3C Validator
Categories
(Core :: DOM: Editor, enhancement, P3)
Tracking
()
VERIFIED
FIXED
mozilla0.9.4
People
(Reporter: peterlubczynski-bugs, Assigned: akkzilla)
Details
(Whiteboard: FIX IN HAND)
Attachments
(2 files)
4.72 KB,
patch
|
Details | Diff | Splinter Review | |
2.72 KB,
patch
|
Details | Diff | Splinter Review |
It would be really nice to include a link to the W3C HTML Validation Service in
Composer to help people write correct HTML. The validator can be found at:
http://validator.w3.org/ and there's a nice place for this link would be under
the Edit menu, next to Check Spelling.
Reporter | ||
Comment 1•25 years ago
|
||
oops, I mean Composer not Compositor.
Assignee: kmcclusk → beppe
Component: Compositor → Editor
QA Contact: petersen → sujay
Comment 2•25 years ago
|
||
good idea, but we have an internal parser that also validates, but setting to
future for consideration after rtm
Target Milestone: --- → Future
Comment 4•24 years ago
|
||
the goal is to do the following:
1. add a menu item under Edit -- Check Document
2. when Check Document is selected, a browser window will be opened, the
document http://validator.w3.org/file-upload.html will be displayed with the
file name added to the File: field.
3. the user seelcts Validate this document button
an alternative solution would be to wrap the W3C validation tool with our
application, allowing for offline validation.
Comment 5•24 years ago
|
||
moving to 1.0 and assigning to akkana
Akkana, the last discussion about this incliuded the following:
When the user selects Edit|Validate, a browser window sould be opened, the local
path name of the file should be sent to the validation tool and inserted in the
text field (this could be accomplished by having a local copy of the initial
validation page and populating it with the pathname). I would suspect there is
some way where the submission of that page could also be triggered without user
interaction. Ryan attempted to try and figure that out, but got stuck on that
function.
Assignee: beppe → akkana
Status: ASSIGNED → NEW
Target Milestone: Future → mozilla1.0
Assignee | ||
Comment 6•24 years ago
|
||
Here's the patch. Does it do everything it needs to? If so, it's ready for review.
Status: NEW → ASSIGNED
Whiteboard: FIX IN HAND
Assignee | ||
Comment 7•24 years ago
|
||
Assignee | ||
Comment 8•24 years ago
|
||
Oh, forgot to mention: this has only been tested on linux so far. In theory it
should work on all platforms, but we need to make sure, especially mac. It
might be that document.location.pathname doesn't map to local file syntax, in
which case I'll probably need platform help to figure out how to map to platform
file names.
Kathy, when you have some time, can you try this patch on mac and see what sort
of file name appears in the window, and whether it works as intended?
I've removed the commented out section in nsValidateCommand.doCommand -- forgot
to remove it before I made the patch (doesn't matter for testing, just code
prettiness).
Comment 9•24 years ago
|
||
beppe, it is probably a bad idea to do automatic uploading for privacy reasons.
Assignee | ||
Comment 10•24 years ago
|
||
This is a user-initiated action, and even after selecting the menu item, the
user has to click a submit button in the validator window before the validator
actually sees the contents of the file. Neither the filename nor the contents
are sent out on the net until the user has done this.
Does that help with the privacy issue, Daniel? Or are there other precautions
we should take, or warnings we should offer the user?
Comment 11•24 years ago
|
||
Maybe I exagerated. When thinking of it I don't see the problem. The user will
obviously be aware of the upload.
Assignee | ||
Updated•24 years ago
|
Target Milestone: mozilla1.0 → mozilla0.9.4
Assignee | ||
Comment 12•24 years ago
|
||
Cc msanz for localization of new menu item.
Assignee | ||
Comment 13•24 years ago
|
||
Using this, I noticed that sometimes I wanted to validate a page before I'd
modified it locally, or after publishing. We should be able to validate from
the web as well as from a local file. So I updated the code to be smarter about
that and handle both the file: and the everything-else cases. See the new patch.
Assignee | ||
Comment 14•24 years ago
|
||
Assignee | ||
Comment 15•24 years ago
|
||
Fix is in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•