1535068 - Custom context menu not displayed in Feedbro addon interface

Status: RESOLVED DUPLICATE of bug 1533630

(Core :: DOM: Events, defect)

Description

[gwarser]

Attachment: bisection.txt

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

Steps to reproduce:

• clean Firefox beta 66 or Nightly 67 profile
• install Feedbro addon (3.39.0)
• open addon interface by clicking on addon icon -> Open Feed Reader
• add new feed:
  • click on "Add a new feed" icon
  • paste https://planet.mozilla.org/atom.xml into "Feed URL" (or any other RSS feed URL)
  • type some name in "Title"
  • click "Save" button
• right click on feed name in "tree view" in sidebar on left hand side

Actual results:

In current beta and Nightly, context menu does not appear at all or only flashes for fraction of a second.

Expected results:

Context menu with feed related option should appear. This is working in current stable 65.0.1

Bisection pointed to: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=f6eebcc14c22762f521fb567a9588963b8720592&tochange=61570c16c2d564c24fab36713fb169c4144453e9

I had some problems with specifying latest stable build and I had to retry with --good 64. Please see attached log.

This happens on Linux Manjaro KDE 2019-03-12

Comment 1

[Gingerbread Man]

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0
20190313100914

Works for me. Setting platform to Linux.

Comment 2

[Olli Pettay [:smaug][[e-mail]]]

The addon expects the old click handling on <button> element where click target was always button element? Now the target can be something inside the <button>

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

Ah, no <button>, but contextmenu is there if one keeps right button down.

Comment 4

[Olli Pettay [:smaug][[e-mail]]]

Ah, it there is now click event, which the addon doesn't expect.
bug 1533630 might help here.

Comment 5

[Olli Pettay [:smaug][[e-mail]]]

Tested locally, and bug 1533630 should fix this.

Comment 6

[voltron]

When can we expect a fix? This bug is seriously breaking our extension on Linux and it's not easy to get around it since it affects a 3rd party library that we use.

Comment 7

[voltron]

Interestingly if you set preference "ui.context_menus.after_mouseup" to true in about:config, then things work correctly. This should be the default behaviour.

Comment 8

[gwarser]

(In reply to voltron from comment #7)

Interestingly if you set preference "ui.context_menus.after_mouseup" to true in about:config, then things work correctly. This should be the default behaviour.

I can confirm.