Closed Bug 661742 Opened 9 years ago Closed 5 years ago

Implement Click-to-web


(Thunderbird :: Mail Window Front End, defect, major)

Not set


(Not tracked)



(Reporter: squib, Assigned: mconley)



(Whiteboard: [wontfix?])


(1 file, 3 obsolete files)

In content tabs, there doesn't seem to be a way to navigate back and forward. At minimum, we should add context menu items for them. Hotkeys (alt-left and alt-right) would be nice too. We could also hook up the "back" and "forward" toolbar buttons to navigate the page, but that's probably not necessary in the short term.
Is there a specific use case for this in Thunderbird currently? We originally kept it light weight because the only real uses of content tabs where single/few page versions. Although I guess AMO browsing might now be one case.

At the time we introduced content tabs, we felt that if extensions were providing content tabs which could navigate through sites, as they'd probably also want to think about security UI.
search results tabs is one use case.
Yeah, AMO and the opensearch add-on are the two cases I'm thinking of.
Blocks: 677421
Attached patch Patch v1 (obsolete) — Splinter Review
Here's my first run at giving back/forth capabilities to content tabs, as well as giving the user the ability to open links in content tabs, as well as their default browser.
Assignee: nobody → mconley
Summary: Allow navigating back/forward in content tabs → Implement Click-to-web
Target Milestone: --- → Thunderbird 11.0
Attached patch Patch v2 (obsolete) — Splinter Review
Whoops, forgot to include a new file.
Attachment #579766 - Attachment is obsolete: true
Do we actually want to default to opening links in content tabs? That seems wrong.
Attached patch Patch v3 (obsolete) — Splinter Review
Some bit-rotting issues got fixed in this patch.
Attachment #579783 - Attachment is obsolete: true

Not sure if it's going to be the default yet.  Hopefully, the forthcoming Click-to-web Feature page will tell us more.

Attached patch WIP Patch v3Splinter Review
Moved the URIUtils.js file to somewhere that makes more sense.

We now show an in-content dialog to allow the user to opt-in to Click-to-web.  There's some nonsense wording in there right now that I need to fix still.
Attachment #579817 - Attachment is obsolete: true
(In reply to Mike Conley (:mconley) from comment #8)
> squib:
> Not sure if it's going to be the default yet.  Hopefully, the forthcoming
> Click-to-web Feature page will tell us more.

Url ?

I understood that Jb was going to create that feature page - CC'ing him for more information.

This is on my Todo list. I'll propose a first version ASAP (tonight, maybe).
This bug is being revisited as the App Tab feature for gSoC:, probably as gSoC
Target Milestone: Thunderbird 11.0 → ---
I'd like to suggest that we mark this bug WONTFIX, and that we should just open most web pages in the user's default browser. There's just no way we'll be able to make Thunderbird into a good (or even usable) browser; look at all the work the Firefox team has to do. Even if we found someone to work on this, it'd be quite a bit of code that we'd have to maintain.
Whiteboard: [wontfix?]
Mike: thoughts on comment 14?
Flags: needinfo?(mconley)
Yep, sounds good.
Closed: 5 years ago
Flags: needinfo?(mconley)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.