881083 - [Multizilla] Add a "Validate this page" entry to the Web Development submenu.

Status: RESOLVED FIXED

(SeaMonkey :: UI Design, defect)

Description

[Philip Chee]

Multizilla had an option to validate the current content page with the w3c html validator. I think this is useful enough to add to SeaMonkey. Patch to follow.

Comment 1

[Philip Chee]

Attachment: Patch v1.0 WIP

> +++ b/suite/common/contentAreaClick.js
....
> -      openNewWindowWith(href, doc);
> +      if (window.QueryInterface(Components.interfaces.nsIInterfaceRequestor)
> +                .getInterface(Components.interfaces.nsIWebNavigation)
> +                .QueryInterface(Components.interfaces.nsILoadContext)
> +                .usePrivateBrowsing)
> +        openNewPrivateWith(href, doc);
> +      else
> +        openNewWindowWith(href, doc);

PB leak!

> +++ b/suite/browser/webDeveloperOverlay.js
> +    var checkURL = "http://validator.w3.org/check?" +
> +                   "charset=%28detect+automatically%29&doctype=Inline&uri=" +
> +                   encodeURIComponent(uri.spec);

TODO move checkURL to a localized string pref.

> +    if (!openNewTabOrWindow(aEvent, checkURL, getBrowser().contentDocument))
How to get openNewTabOrWindow() to open the tab/window in the foreground?

> +      getBrowser().addTab(checkURL, { referrerURI: uri, focusNewTab: true });
Fallback.

> +  initOverlay: function initOverlay(aEvent) {
> +    window.removeEventListener("load", gWebDeveloper.initOverlay, false);

I should remove the event listener from safeBrowsingOverlay.js as well shouldn't I?

> +  <menupopup id="toolsPopup">
> +    <menuitem id="validatePage"
Should I put this under the Web Development menu or directly on the main Tools menu?
TODO add the CSS checker and link checker from Bug 102952.

While filing this bug, Bugzilla's duplicate checker helpfully pointed me to Bug 102952 ([RFE] Validate HTML should be available in the browser) which was WONTFIXed.

Comment 2

[[e-mail]]

(In reply to Philip Chee from comment #1)
> > +      if (window.QueryInterface(Components.interfaces.nsIInterfaceRequestor)
> > +                .getInterface(Components.interfaces.nsIWebNavigation)
> > +                .QueryInterface(Components.interfaces.nsILoadContext)
> > +                .usePrivateBrowsing)
> > +        openNewPrivateWith(href, doc);
> > +      else
> > +        openNewWindowWith(href, doc);
> 
> PB leak!

[It's safe to use if (gPrivate) here.]

> > +    if (!openNewTabOrWindow(aEvent, checkURL, getBrowser().contentDocument))
> How to get openNewTabOrWindow() to open the tab/window in the foreground?
Windows always open in the foreground, tabs depend on the shift key.

Comment 3

[Philip Chee]

Attachment: Patch v1.1 address feedback.

Changes since the last patch:
1. use gPrivate in openNewTabOrWindow().
2. Moved checkURL to a localized string pref.

Comment 4

[Philip Chee]

Pushed to comm-central:
http://hg.mozilla.org/comm-central/rev/df887839a810

Comment 5

[[e-mail]]

Comment on attachment 761029 [details] [diff] [review]
Patch v1.1 address feedback.

>+    if (!openNewTabOrWindow(aEvent, checkURL, getBrowser().contentDocument))
>+      getBrowser().addTab(checkURL, { referrerURI: uri, focusNewTab: true });
openUILink is a better fit.

>+  initMenuItem: function initMenuItem() {
>+    var menuitem = document.getElementById("validatePage");
>+    var uri = getBrowser().currentURI;
It looks as if your overlay doesn't apply to the Mac hidden window, which (if true) is good.

>+  initOverlay: function initOverlay(aEvent) {
[This of course gets called as a global method, which is why you have to use gWebDeveloper rather than this... it's fortunate that you only need to refer to it twice.]

>+      if (gPrivate)
>+        openNewPrivateWith(href, doc);
>+      else
>+        openNewWindowWith(href, doc);
I guess this really ought to land on branches...