Open Bug 1678744 (proton-address-bar) Opened 4 years ago Updated 1 year ago

[meta] Proton - Address bar work

Categories

(Firefox :: Address Bar, task, P2)

Product:
Firefox
Component:
Address Bar
Type:
task

Tracking

()

People

(Reporter: mconley, Unassigned)

References

(Depends on 13 open bugs, Blocks 1 open bug)

Details

(Keywords: feature-testing-meta, meta)

This metabug tracks work that applies to the AwesomeBar for the Proton visual refresh.

Blocks: proton
Severity: -- → N/A
Priority: -- → P2
Depends on: 1687397
Depends on: 1689200
No longer depends on: 1690573
Depends on: 1691436
Depends on: 1691454
Depends on: 1691464
Depends on: 1691465
Depends on: 1691474
Depends on: 1691530
Depends on: 1691531
Depends on: 1691533
Depends on: 1691534
Depends on: 1691535
Depends on: 1691537
Depends on: 1691542
Depends on: 1691543
Depends on: 1691544
Depends on: 1691545
Depends on: 1691743
Depends on: 1616700
Depends on: 1691911
Depends on: 1691912
Depends on: 1691993
Depends on: 1692046
Depends on: 1692215
Depends on: 1692216
Depends on: 1692218
Depends on: 1692223

I am seeing when the urlbar is in focus the outline/border does not appear any longer. Without the outline, the background and the input box are the same color and can confuse user as to where to type. I filed a bug here https://bugzilla.mozilla.org/show_bug.cgi?id=1692554 concerning this with an image to show what I mean.

it's not yet the time to enable the address bar work, it's totally incomplete. Please don't use it, we'll enable it when it's the time.

(In reply to Marco Bonardo [:mak] from comment #3)

it's not yet the time to enable the address bar work, it's totally incomplete. Please don't use it, we'll enable it when it's the time.

I don't understand this statement! is it not what we are supposed to do? find and report bugs, test and report progress whether or not its positive or negative? Not the time to enable, in NIGHTLY? The point of Nightly is to do just that, TEST, Report, and FIX or am I wrong?

(In reply to Troy Janda from comment #4)

I don't understand this statement! is it not what we are supposed to do? find and report bugs, test and report progress whether or not its positive or negative? Not the time to enable, in NIGHTLY? The point of Nightly is to do just that, TEST, Report, and FIX or am I wrong?

It depends on the state of the work. The work here is still in the very early stages, so it's a bit like having people taste raw cake batter and report that it doesn't taste or look like a cake yet. Towards the latter stages, where the big changes start slowing down, and the development team starts getting into the finer detail and polish work is probably a better time.

(In reply to Mike Conley (:mconley) (:⚙️) (Catching up on needinfos) from comment #5)

(In reply to Troy Janda from comment #4)

I don't understand this statement! is it not what we are supposed to do? find and report bugs, test and report progress whether or not its positive or negative? Not the time to enable, in NIGHTLY? The point of Nightly is to do just that, TEST, Report, and FIX or am I wrong?

It depends on the state of the work. The work here is still in the very early stages, so it's a bit like having people taste raw cake batter and report that it doesn't taste or look like a cake yet. Towards the latter stages, where the big changes start slowing down, and the development team starts getting into the finer detail and polish work is probably a better time.

Yes but when the cake batter breaks something else its needs to be reported if for nothing else than to just bring attention to the breakage. many times little changes cause an issue and by the time its reported can be lost. to dismiss as invalid seems radical and defeats the purpose of having a dev build.

According to the plan, there will be a full Nightly cycle to test Proton, and it's possible we'll enable address bar changes earlier than that. There will be time for testing.
The changes are kept behind an hidden pref because they are bogus yet, reporting bugs before we flip the pref would just waste your and our time, because the bugs are caused by missing work. I picked invalid because bugzilla doesn't provide me with a "not-yet-the-time" resolution, nothing personal.

Depends on: 1693376
No longer depends on: 1689200
Depends on: 1694754
Depends on: 1695276
Depends on: 1696469
Depends on: 1696479
Depends on: 1696480
Depends on: 1696628
No longer depends on: 1696628
Depends on: 1696628
Depends on: 1696932
Depends on: 1695022
Depends on: 1697191
Depends on: 1697415
Depends on: 1697426
Depends on: 1697499
Depends on: 1697801
Depends on: 1695061
Depends on: 1697913
Depends on: 1698640
Depends on: 1698692
Depends on: 1698814
Depends on: 1698834
No longer depends on: 1698814
Depends on: 1698986
Depends on: 1699226
Depends on: 1699407
Depends on: 1699465
Depends on: 1699557
Depends on: 1699806
Depends on: 1700137
Depends on: 1700364
Depends on: 1700582
Depends on: 1700374
Depends on: 1699229
Depends on: 1701544
Depends on: 1701548
No longer depends on: 1701544
No longer depends on: 1701548
Depends on: 1701629
Depends on: 1699834
Depends on: 1702018
Depends on: 1702034
Depends on: 1702237
Depends on: 1702241
Depends on: 1700527
Blocks: 1702442
Depends on: 1702769
Depends on: 1702770
Depends on: 1702772
Depends on: 1702773
Depends on: 1702774
Depends on: 1702775
Depends on: 1702777
Depends on: 1703036
Depends on: 1703274
Depends on: 1703590
Depends on: 1703647
Depends on: 1703889
Depends on: 1703898
Depends on: 1703925

Please link bug 1703932 to this report. Thanks :)

Depends on: 1703932
Depends on: 1704087
Depends on: 1704414
Depends on: 1704474
Depends on: 1704795
Depends on: 1705072
Depends on: 1704752
Depends on: 1704982
Depends on: 1705323
Depends on: 1705379
Depends on: 1705449
Depends on: 1705562
Depends on: 1705814
Depends on: 1706112
Depends on: 1706117
Depends on: 1706154
Depends on: 1706232
Depends on: 1706321
Depends on: 1706326
Depends on: 1706334
No longer depends on: 1706232
Depends on: 1706363

Bookmark button needs to be updated, please take a look https://bugzilla.mozilla.org/show_bug.cgi?id=1706437

Depends on: 1706470
Depends on: 1707012
Depends on: 1707053
Depends on: 1705723
Depends on: 1705572
Depends on: 1707756
Depends on: 1707604
Depends on: 1707839
Depends on: 1706479
Depends on: 1707424
Depends on: 1707949
Depends on: 1707947
Depends on: 1708158

Can you please link bug 1708263 to this one? Thanks :)

Depends on: 1708263
Depends on: 1708281
Depends on: 1708530
Depends on: 1708533
Depends on: 1708799
Depends on: 1708879
Depends on: 1708960
Depends on: 1709238
Depends on: 1709400
Depends on: 1709405
Depends on: 1709512
No longer depends on: 1708158
Depends on: 1708554
Depends on: 1710612
Depends on: 1710651
Depends on: 1710932
Depends on: 1711139
Depends on: 1711231
Depends on: 1711241
Depends on: 1711245
No longer depends on: 1711241
Depends on: 1711689
Depends on: 1712569
Depends on: 1712775
Depends on: 1713310
Depends on: 1713953
Blocks: 1716528
No longer blocks: 1716528
No longer depends on: 1722625
No longer depends on: 1724956
Depends on: 1827391
You need to log in before you can comment on or make changes to this bug.