JSView 2.0.8-mod for SeaMonkey 2.1+ and Firefox 4+

[uilym]

Nice work Phil. Thank you so much. I'm glad to have my JSView back.

[brandycruzn]

Your a lifesaver Phil! Thanks heaps!

[NanM]

Hi Phil,
Just an update for 4 Beta:
Works fine.

Minor UI annoyance:

Known issues:

• I don't have suitable graphics for the selector buttons in the Firefox PageInfo window so all you get is the generic squished PageInfo button.

Phil

The generic button has morphed into a double line of *all* the alternative icons for this UI - - makes for a very busy menu bar now

thanks for your work.

[Philip Chee]

The generic button has morphed into a double line of *all* the alternative icons for this UI - - makes for a very busy menu bar now

Eeek. I've pushed out a CSS fix: http://downloads.mozdev.org/xsidebar/mods/jsview-2.0.6a1-mod.xpi. I'm leaving it as an alpha until Firefox 4.0 final is out because who knows what may break until then.

FWIW. I think this is due to the Firefox PageInfo Window linking to the Addons Manager stylesheet. With the Addons Manager disappearing and becoming about:addons, that CSS doesn't exist any more.

Phil

[NanM]

Eeek. I've pushed out a CSS fix [...] I'm leaving it as an alpha until Firefox 4.0 final is out because who knows what may break until then.

Noted.
I does sound like quite a few UI changes are brewing still.

[Philip Chee]

Eeek. I've pushed out a CSS fix [...] I'm leaving it as an alpha until Firefox 4.0 final is out because who knows what may break until then.

Noted.
I does sound like quite a few UI changes are brewing still.

Not only that. Once multiprocess tabs land a lot (and I mean a lot) of extensions will break. Frankly I'm not confident if I can keep JSView running then.

Phil

[NanM]

Eeek. I've pushed out a CSS fix [...] I'm leaving it as an alpha until Firefox 4.0 final is out because who knows what may break until then.

Noted.
I does sound like quite a few UI changes are brewing still.

Not only that. Once multiprocess tabs land a lot (and I mean a lot) of extensions will break. Frankly I'm not confident if I can keep JSView running then.

Phil

Understood.
However things pan out, your coding on JSView would've been no less welcome for even this brief resurrection
Am sort of banking on an extended support period from Mozilla for 3.6.x here; regret very much the moves to "simplify" and "streamline" and to more closely manage users. Much prefer the older more anarchic ecosystem.

[Philip Chee]

http://xsidebar.mozdev.org/modifiedmisc.html#jsview
I've pushed out JSView 2.0.6-mod with a minor view source fix for SeaMonkey 2.1 which is now using the same Toolkit view source code as Firefox. No changes were made for Firefox but now that Firefox 4.0 is scheduled for Tuesday 22nd March, I thought it would be a good time to formally issue an update.

Phil

[NanM]

http://xsidebar.mozdev.org/modifiedmisc.html#jsview
I've pushed out JSView 2.0.6-mod with a minor view source fix for SeaMonkey 2.1 [...]No changes were made for Firefox but now that Firefox 4.0 is scheduled for Tuesday 22nd March, I thought it would be a good time to formally issue an update.

Phil

Thanks so much Phil. Hope you and SeaMonkey continue to protect the true faith

[Alan Baxter]

jsview-2.0.6-mod isn't compatible with Fx 5.0, Phil. Does it just need a bump or will a code change be needed first?

[Philip Chee]

jsview-2.0.6-mod isn't compatible with Fx 5.0, Phil. Does it just need a bump or will a code change be needed first?

A version bump should be enough. No time to test though. But if you confirm then I'll do it here.

Phil

[Alan Baxter]

All the functions seem to work in Fx 5.0. I think it's safe to bump it to 5.*

[therube]

(Not that I care or even have tested, but) http://xsidebar.mozdev.org/modifiedmisc.html#jsview could probably stand that version bump for (Firefox).

Confirmed, works (in FF5).

---

Oddities, but not worth messing with IMO.

Right-click the icon, About JSView, shows as v2.0.5 & also generates an Error Console error:

Code: Select all

Error: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIFileProtocolHandler.getFileFromURLSpec]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: chrome://jsview/content/jsviewAbout.js :: <TOP_LEVEL> :: line 73"  data: no]

(Eh, but who knows. Maybe such a thing could cause leakage?)

[Philip Chee]

(Not that I care or even have tested, but) http://xsidebar.mozdev.org/modifiedmisc.html#jsview could probably stand that version bump for (Firefox).

Confirmed, works (in FF5).

I've bumped the maxVersion to 20.* (fingers crossed!)

Oddities, but not worth messing with IMO.

Right-click the icon, About JSView, shows as v2.0.5 & also generates an Error Console error:

Code: Select all

Error: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIFileProtocolHandler.getFileFromURLSpec]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: chrome://jsview/content/jsviewAbout.js :: <TOP_LEVEL> :: line 73"  data: no]

(Eh, but who knows. Maybe such a thing could cause leakage?)

Um yeah, In Firefox 4+ the extension XPI isn't unpacked by default so JSView can't find the files containing the translator names. I've set the <em:unpack> flag to true in the install.rdf as a quick workaround.

Phil

[therube]

Thank you .