Closed Bug 1199692 Opened 9 years ago Closed 6 years ago

Clicking learn more for a tile navigates away in the same page and could make the tile unreachable

Categories

(Firefox :: New Tab Page, defect, P1)

defect

Tracking

()

RESOLVED INVALID

People

(Reporter: mstorm, Assigned: emtwo)

Details

Attachments

(2 files)

Hey Nan and Kevin, 

When you click to learn more on a content tile description and it take to the page explaining content it loads in the same page so the user looses the tile and can't click on it. 

Can we have the link open in a new tab so when the user clicks on it they still have a chance to click on the content?

Thanks, 

~Storm
Hey Matt,

There is no control on that behavior from the server side.
Looped in Marina as this has to do with Firefox, she might know what's the best solution to it.


Thanks,
Nan
This would be handled from Firefox.
Assignee: najiang → nobody
Group: mozilla-employee-confidential
Component: Tiles → New Tab Page
Product: Content Services → Firefox
This is especially bad for tiles with a frequency cap of 1, so the user wouldn't see the tile again.
Summary: Content Tiles: User experience bug → Clicking learn more for a tile navigates away in the same page and could make the tile unreachable
I think just opening the link in a new tab avoids this issue.
Attachment #8654212 - Flags: review?(edilee)
Comment on attachment 8654212 [details] [diff] [review]
Part 1: v1: Open 'Learn more' link in a new tab

Test would be good to make sure this functionality persists.
Attachment #8654212 - Flags: review?(edilee) → review+
Assignee: nobody → msamuel
Attached patch Part 2: v1: TestSplinter Review
Attachment #8655011 - Flags: review?(edilee)
Attachment #8654212 - Attachment description: v1: Open 'Learn more' link in a new tab → Part 1: v1: Open 'Learn more' link in a new tab
Comment on attachment 8655011 [details] [diff] [review]
Part 2: v1: Test

>+    frecent_sites: ["classroom.google.com", ...
Probably could have just tested with a plain sponsored directory tile, but this works too.

>+  registerCleanupFunction(() => {
>+    NewTabUtils.isTopPlacesSite; origIsTopPlacesSite;
Missing an assignment operator.

>+    let onTabOpen = function(event) {
>+      container.removeEventListener("TabOpen", onTabOpen, false);
>+      let browser = gBrowser.getBrowserForTab(event.target);
>+      browser.addEventListener("load", () => {
>+        browser.removeEventListener("load", this, true);
>+        is(browser.currentURI.spec, "about:blank", "We opened 'about:blank' after clicking 'Learn more'");
>+        is(gBrowser.tabs.length, 3, "There are now 3 tabs open");
>+        is(gBrowser.getBrowserForTab(gBrowser.tabs[1]).currentURI.spec, "about:newtab", "about:newtab is still open");
Probably good hygiene to close the extra tab unless head_* closes extra tabs already.

>+  promise.then(() => { TestRunner.next; });
Should be able to just do promise.then(TestRunner.next)
Attachment #8655011 - Flags: review?(edilee) → review+
Backed out for causing frequent Win8 browser_private_search_perwindowpb.js timeouts followed by a cascade of other failures.
https://treeherder.mozilla.org/logviewer.html#?job_id=4483253&repo=fx-team

https://hg.mozilla.org/integration/fx-team/rev/e5d0ef8da5b0
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: