Closed Bug 56061 Opened 24 years ago Closed 21 years ago

about:about

Categories

(SeaMonkey :: UI Design, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rbs, Assigned: caillon)

References

Details

Attachments

(1 file, 1 obsolete file)

RFE to display a clickable list of all the supported about:*
Target Milestone: --- → Future
Neat idea.
Keywords: helpwanted
I'd like to do it. :)
mass move, v2. qa to me.
QA Contact: tever → benc
See also bug 87513, error page for about:foo (where foo isn't recognized).
does this belong in the help component?
I can do this, I will make one based on all that is currently in the tree.
Having about:about would certainly make my life easier, I would not need to write a test document for about by hand.
Keywords: mozilla1.0
Blocks: 96712
Faking it using Mozilla keywords! http://www.mozilla.org/docs/end-user/keywords.html Create a bookmark as normal to whatever it is you want Then go to bookmark properties set the keyword to about:about Now if you type about:about in the location bar mozilla will automagically follow your link.
I also think this should be included under the Help menu, since it should be pretty visible in order to be effective.
-> XP apps. Someone needs to create content in a patch and checkin. Not much networking to be done here...
Assignee: gagan → sgehani
Component: Networking → XP Apps
QA Contact: benc → paw
Just stumbled in bug 140034: about:buildconfig These days, there are so many about:* that it is virtually impossible to discover/stumble on all of them, let alone remember them. It is getting to the point that this bug isn't just an 'enhancement' anymore. Not being able to discover the about:* options means that not being able to use them.
Taking. I just hacked up a quick implementation of this. I'll need to do some cleaning up before I post an actual patch, but should be out the door relatively soon.
Assignee: sgehani → caillon
Target Milestone: Future → ---
Okay, I just stumbled across a minor roadblock. http://lxr.mozilla.org/mozilla/source/caps/src/nsScriptSecurityManager.cpp#1230 prevents me from linking to most about: URLs. What I have will display all abouts and give you links, but only a couple (about:, about:blank, about:mozilla) are actually clickable....
Attached patch First crack at this (obsolete) (deleted) — Splinter Review
This seems to play nicely now.
Comment on attachment 121598 [details] [diff] [review] First crack at this Oh, btw: I don't really care much to do work beyond where I have it other than review comment updates. If someone wants to make this localizable, or figure out a way to tell if a link is unusable as listed (such as about:cache-entry which requires ?querystring params), be my guest. I just want to get a review, super-review, and once I do, I'll get a security review and land this, and any other work can be done at that point. Unless someone wants to modify the patch. >Index: xpfe/global/resources/content/aboutAbout.html >=================================================================== >+ var referrer; >+ try { >+ referrer = Components.classes["@mozilla.org/network/standard-url;1"].createInstance(Components.interfaces.nsIURI); >+ referrer.spec = "chrome://global/content/aboutAbout.html"; >+ } catch (e) { >+ referrer = { spec: "chrome://global/content/aboutAbout.html" }; >+ } The above code snippet was inadvertently left in and should be removed, btw.
Attached patch Patch (deleted) — Splinter Review
Also includes a minor change to caps to allow chrome (resource) uris to link to about: uris.
Attachment #121598 - Attachment is obsolete: true
Comment on attachment 128064 [details] [diff] [review] Patch r/sr=darin this looks good to me. you probably want to get someone more familiar with xpfe-land like jag to review this as well.
Attachment #128064 - Flags: superreview+
Attachment #128064 - Flags: review?(bryner) → review+
Let there be about:about.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
re - { "about", DenyProtocol }, + { "about", ChromeProtocol }, and comment 13: Who made the security review? IIRC, we had exploits in about: and strong restrictions were the fix.
Darin looked at it, but here's the explanation. The exploits were because it was set to AllowProtocol meaning the world could link to about: URIs. This is completely safe because it still restricts the linking to only ChromeProtocol URIs (only chrome: or resource:) For reference, the about: exploit bug was bug 91714.
Yes, it seems to be safe. Thanks for the answer. FYI, I was thinking about bug 134315 (and others, IIRC).
Product: Core → Mozilla Application Suite
Blocks: 220253
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: