Closed Bug 1909211 Opened 1 year ago Closed 1 year ago

Add Bookmark dialog suggests all already entered tags instead those ones related to the one being currently entered

Categories

(Firefox :: Bookmarks & History, defect, P2)

Firefox 128
defect

Tracking

()

VERIFIED FIXED
130 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- verified
firefox128 --- wontfix
firefox129 --- wontfix
firefox130 --- verified

People

(Reporter: hawran.diskuse, Assigned: mak)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [sng][places-regression])

Attachments

(2 files)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0

Steps to reproduce:

  1. Add a bookmark (ctrl+d).
  2. Enter a couple of tags.

Actual results:

The edit field for tags shows (suggests? autocompletes?) all tags already entered with a bookmark being added instead of just (all existing) tags related to a tag being added.
When the edit field is full of tags, the new tag is not shown.

Expected results:

Before this update the edit field suggested (autocompleted) all existitng tags, however just related to the tag being entered.

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0
OS: Linux 6.5.0-44-generic #44~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jun 18 14:36:16 UTC 2

The Bugbug bot thinks this bug should belong to the 'Firefox::Bookmarks & History' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Bookmarks & History

This happens not only in the "Add bookmark" dialogue, but also in the bookmarks manager (when editing a single bookmark's tags); in "Add bookmark" it's far more annoying since the tag input field and the associated dropdown are so narrow.

I'm seeing this behaviour in the Windows version of Firefox (127.0.2), too.

This is apparently really a regression in Firefox 127.0 - just to be sure, I've re-installed 126.0.1 (firefox/releases/126.0.1/linux-x86_64/en-US/firefox-126.0.1.tar.bz2), and it doesn't show this behaviour.

I'm sorry, but I got really confused about the version numbers - I somehow believed I was on 127.0.2, while I'm actually on 128.0.2.

I re-tested the previous release (firefox/releases/127.0.2/linux-x86_64/en-US/firefox-127.0.2.tar.bz2), and the behaviour didn't occur - so the bug apparently first appears in 128.0.

Sorry about the confusion.

I ran mozregression and found this is a regression from Bug 1886064.

The TaggingService uses AutoCompleteSimpleResult instance's AppendMatch

  void appendMatch(in AString aValue,
                   in AString aComment,
                   [optional] in AString aImage,
                   [optional] in AString aStyle,
                   [optional] in AString aFinalCompleteValue,
                   [optional] in AString aLabel);

We're passing this._result.appendMatch(before + tag, tag);
It looks like the new behavior requires us to pass tag as aLabel instead of aComment.

Severity: -- → S4
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
Priority: -- → P2
Regressed by: 1886064
Whiteboard: [sng][places-regression]

Set release status flags based on info from the regressing bug 1886064

:enndeakin, since you are the author of the regressor, bug 1886064, could you take a look?

For more information, please visit BugBot documentation.

This is trivial, though I'd like to check our testing story.

Assignee: nobody → mak
Status: NEW → ASSIGNED
Flags: needinfo?(enndeakin)
Pushed by mak77@bonardo.net: https://hg.mozilla.org/integration/autoland/rev/693fe3b405c1 Bookmark dialogs suggests all already entered tags instead of just the new matching one. r=daisuke,places-reviewers
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch

The patch landed in nightly and beta is affected.
:mak, is this bug important enough to require an uplift?

  • If yes, please nominate the patch for beta approval.
  • If no, please set status-firefox129 to wontfix.

For more information, please visit BugBot documentation.

Flags: needinfo?(mak)

we're in RC week, not worth uplifting to beta.
We should consider ESR though.

Flags: needinfo?(mak)
Attachment #9417256 - Flags: approval-mozilla-esr128?

esr128 Uplift Approval Request

  • User impact if declined: Bookmark tags autocomplete malfunctioning
  • Code covered by automated testing: yes
  • Fix verified in Nightly: no
  • Needs manual QE test: yes
  • Steps to reproduce for manual QE testing: Typing more than one tag should only show the last tag in the autocomplete panel
  • Risk associated with taking this patch: low
  • Explanation of risk level: single line fix, adapting to the underlying code changes
  • String changes made/needed: none
  • Is Android affected?: no
Flags: qe-verify+
Attachment #9417256 - Flags: approval-mozilla-esr128? → approval-mozilla-esr128+

I have reproduced this issue using an affected Nightly build 2024-07-22 with STR from comment 0.

The issue is verified as fixed on FirefoxEsr 128.2.0 and RC1 130 under macOS 14, Ubuntu 22 and Win 11.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
Duplicate of this bug: 1912457
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: