New issue
Advanced search Search tips

Issue 787583 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Build links should open in new tabs

Project Member Reported by rsesek@chromium.org, Nov 21 2017

Issue description

luci, working for the Chromium project.
built: 2017-11-21 4:22 PM (EST)
version: 2392-5dafc74

What steps will reproduce the problem?
(1) Go to https://ci.chromium.org/p/chromium/g/main/console
(2) Click on a build link
(3) It navigates away from the console

What is the expected result?
Open the build in a new tab.

What happens instead?
The console navigates to the build details page.

The old waterfall did a little popup-thing to show the build status, and then clicking on a build would open in a new tab/window.

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 

Comment 1 by estaab@chromium.org, Nov 21 2017

Hi, can we get a little more info to help us understand what we can do to make this better?

In particular, what have you lost from your previous workflow? Does it take a lot longer to get to some info you need?

We won't be able to replicate all of buildbot's behavior but we don't want to negatively impact anyone's productivity either.

Thanks!

Comment 2 by efoo@chromium.org, Nov 22 2017

Labels: LUCI-Blocker-UI
Adding tracking label

Comment 3 by efoo@chromium.org, Nov 22 2017

Labels: LUCI-KnownIssues-UI

Comment 4 by rsesek@chromium.org, Nov 22 2017

I don't really miss the popup thing that Buildbot had. But the console is a pretty large page, and I frequently want to open up several failing builds to inspect. I just forget to hold down Cmd to open the build links in new tabs, because Buildbot used to target=_blank them.

Comment 5 by estaab@chromium.org, Nov 27 2017

Labels: -LUCI-Blocker-UI
Status: Available (was: Untriaged)
That makes sense. I think there will be a handful of migration pain points that will come from moving to a new UI. I'm not totally sold that the target=_blank behavior is better since ctrl/cmd is an option this way and the opposite isn't if we change it back.

We can keep this open as a known issue and see if others don't like the change in behavior and go from there. Thanks!
Project Member

Comment 6 by sheriffbot@chromium.org, Nov 28

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
It's been a year and there's 1 star on this bug and no other bugs have been files about the existing behavior.  I'll conclude that the present behavior is okay, and mark this bug as WontFix.

Personally I think setting target=_blank for links should only be used for extraordinary cases, such as linking out of a domain.  In my opinion, linking to builds from the console doesn't meet this bar.
It is easy for a user to choose to open a link in a new tab, but a user can't choose to open a target=_blank link in the current window.

Sign in to add a comment