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

Steps to reproduce:

1. Open `about:config`, find `layout.css.devPixelsPerPx` and change the value from default (-1.0) to 1.2.
2. Open a view-source view with long lines: `view-source:https://www.youtube.com/user/10asti10`
3. hit Ctrl+f, search for rss
4. using the LMB, try selecting some text, then copy and paste it somewhere

Actual results:

After step 3, the highlighted text on the page is not ”rss”. The highlight doesn’t even adhere to letter widths (screenshot 1).

After step 4, the pasted text is not even close to what you’ve selected to copy.

Expected results:

For the search to hightlight an occurence of ”rss”, and for the pasted text to correspond to what I’ve selected from the view-source view.

== The issue ==
Search and text selection highlighting visuals get mismatched with the actual selection in view-source when the value of `layout.css.devPixelsPerPx` is 1.2 or larger.

== Steps to reproduce ==
* Open `about:config`, find `layout.css.devPixelsPerPx` and change the value from default (-1.0) to 1.2.
* Open a view-source view with long lines: `view-source:https://www.youtube.com/user/10asti10`
* hit Ctrl+f, search for rss
* using the LMB, try selecting some text, then copy and paste it somewhere

== What happens ==
Screenshot 1: the highlighted text on the page is not ”rss”. The highlight doesn’t even adhere to letter widths.

Screenshot 2: the pasted text is not even close to what you’ve selected to copy.

== What I expect to happen ==
For the search to hightlight an occurence of ”rss”, and for the pasted text to correspond to what I’ve selected from the view-source view.

== Other info ==
* In my testing, a devPixelsPerPx value of 1.1 seems to not trigger this, whereas 1.2 and anything above does.
* In addition to 18.04 (whence the attached info is from) I’ve reproduced this in a VM running up-to-date 18.10.

Alright, from my brief testing it would seem this does not reproduce under Wayland.

My recipe above appears to be quite sensitive to details: I have a test user with a clean desktop (with little more customization apart from the extension), and there the recipe works just as written. On the other hand, with my main user account it doesn’t. To clarify: while the steps listed above fail to reproduce the issue with my main account, my main account does manifest the issue too; just not with those exact steps.

My main account starts up the Signal desktop client, Nextcloud client and some other stuff upon login, but so far I haven’t found which of those (if any) causes this difference.

I was, however, able to reproduce the ”see-through hole” effect under both accounts: instead of maximizing Gnome terminal (in step 3), I tile it to cover the left half of my screen, then start up Chrome/Firefox, tile itover the terminal window (i.e. to also cover the left half of the screen), before turning the display off and on again. Firefox then also manifests the hole, as does Gnome terminal when brought back to foreground from below. (Chrome does not manifest the hole, but then again Chrome has always appeared oblivious to the extension here.)

I should mention that I’m leaving the display off for about 4-5 seconds before turning it back on again. I’m not sure if that makes any difference, I’m just doing to to be sure that the ”I’m off” signal has time to propagate back to the system.

Background

I’m using the currently published version of No Title Bar from Gnome Extensions in Ubuntu 18.04 (gnome-shell version 3.28.1-0ubuntu2).

Steps to reproduce

1. log in to desktop
2. start Gnome terminal
3. maximize the terminal window (so that the title bar merges with the activity bar)
4. power the display off, then back on

What happens

The terminal window again has its own title bar.

What I expect to happen

For the terminal window title bar to remain merged with the activity bar.

Further info

Under some circumstances (the specifics of which I haven’t been able to narrow down), when the title bar comes back, it is entirely transparent, so that in place of a title bar you have a see-through hole. Here’s a screenshot, showing how part of Firefox’s UI is visible from behind the terminal window, through where the title bar would be.

Background

I’m using Ubuntu 18.04 with Gnome Shell 3.28.1, and was forwarded here from Launchpad, see bug #1767806 there.

The issue

When another window is maximized or tiled to the left side of the screen, re-opening an application whose window was previously tiled to the left side does not restore that windows’ previous position. Instead such windows open at varying distances from the dock, untiled.

Expected behavior

Steps to reproduce (with a newly created user)

1. open Firefox, drag the window to the left edge of the screen to tile it there (filling up the left half of horizontal screen space)
2. close Firefox
3. open Nautilus, make sure that the window floats (i.e. is unmaximized and not tiled to either side of screen)
4. open Firefox

What happens

As expected, Firefox’s window is tiled to the left edge of screen, immediately to the right side of the dock: screenshot.

Unexpected behavior

Steps to reproduce (with a newly created user)

1. open Firefox, drag the window to the left edge of the screen to tile it there (filling up the left half of horizontal screen space)
2. close Firefox
3. open Nautilus, maximize its window
4. open Firefox

What happens

Firefox’s window opens slightly to the right off the right edge of the dock (with a gap between the dock and the window): screenshot.

What I expect to happen

I expect Firefox’s window to be tiled to the left edge of screen, immediately to the right side of the dock, just as it did following the first recipe above.

Further information

• Either maximizing or tiling Nautilus’ window to the left edge of the screen (at step 3) triggers the issue. Tiling it to the right edge of the screen does not.
• Using Gnome Terminal instead of Nautilus triggers the issue just as well and I suspect any other application will, though I’ve only systematically tested these two so far.
• From battling with this in my daily use I also know that the distance of incorrectly restored windows from the dock varies: different applications open at different distances. The precise mechanics of this still elude me, though the distances do appear to be multiples of 25 pixels.

In addition to Totem, Firefox also exhibits this with fullscreen HTML5 video. Here’s a good test: https://www.youtube.com/watch?v=5xkNy9gfKOg

Haven’t seen this since upgrading to 18.04, and can’t reproduce it following the instructions anymore either, so it appears to be fixed.

Impacted version: 0.60

Server Setup Information:

• Operating System: Ubuntu 16.04
• Deployment Method: snap
• ROOT_URL environment variable (Is there a subfolder?): https://my-domain.com/kan (yes)

Problem description:
A description consisting entirely of a URL that happens to extend from the left edge to the right edge of the description field makes it impossible to edit the description, as clicking anywhere on the viewer lands the click on the URL, which triggers a new browser tab instead of the editor.

Here’s a screenshot of such a URL overlapping the editing area, as highlighted by the inspector in Firefox.

There’s actually a couple of pixels worth of unlinked, clickable editor area at the right edge here, but you need a really steady hand and mouse to hit those pixels.

A workaround seems to be to change the browser zoom level (either way), causing the URL to extend either over to the next line or properly short of the right edge of the first line (turning the rest of the line clickable).

After upgrading to Quantum, the right mouse button context menu for HTML links pops up in the wrong place when the Firefox window is pushed to either side of my screen (so that the window takes up half of the horizontal space). The issue appears similar to what has been reported in bug #1721614 (particularly as it appears in the video attached by the submitter), but for me the issue does not occur with the hamburger menu or other UI elements, only with links on webpages, and the menu highlighting behavior is different: in my issue the highlighting occurs normally only once I point the cursor at the menu.

== Steps to reproduce ==
1. Create a new profile and start Firefox using the profile.
2. Expand the window to fill the screen (if not already).
3. Enter search terms into the URL bar and hit enter to bring up a search results page.
4. Right-click a search result title to bring up the context menu. Left-click outside it to close it.
5. Grab the window title bar and push the window to the right edge of screen to resize the window to span half of screen horizontally. Release the title bar.
4. Right click the search result title again.

== What happens ==
The menu pops up on way off from where the mouse cursor is. See attached screenshot.

== What should happen ==
The context menu should pop up next to mouse cursor.

== Possible culprit ==
This seems to be somehow tied to localization: if I uninstall firefox-locale-*, then create a new Firefox profile, with this new profile the menu pops up where it should. I’m using Finnish locale, but this is reproducible with just firefox-local-en too, although the mispositioning differs between locales (Finnish pushes the menu off to the left, whereas English pushes it down and to the right).

== Workaround ==
Don’t right-click on the page before resizing the window (that is, skip step #4 above). This seems to be the trigger.

== Other info ==
I’m able reproduce this in a (16.04) VM just as well as on the host desktop.

In case the collected data doesn’t include this, my primary display is 2560 × 1440p, and the only display connected. xrandr output:

Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 2560×1440+0+0 (normal left inverted right x axis y axis) 527mm x 296mm
2560×1440 59.95*+
2048×1152 59.90
1920×1200 59.88
1920×1080 60.00 50.00 59.94 24.00 23.98
1920x1080i 60.00 50.00 59.94
1600×1200 60.00
1680×1050 59.95
1280×1024 75.02 60.02
1280×800 59.81
1152×864 75.00
1280×720 60.00 50.00 59.94
1024×768 75.03 60.00
800×600 75.00 60.32
720×576 50.00
720×480 60.00 59.94
640×480 75.00 60.00 59.94
720×400 70.08
HDMI-2 disconnected (normal left inverted right x axis y axis)
HDMI-3 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)

Screenshot with the context menu off to the left of mouse cursor (Finnish locale) Edit (490.3 KiB, image/png)

Sivuston uudistuksen myötä etusivulla nyt olevien uutis-, ilmoitus- ja kuulutusotsikkolinkkien toiminnassa on jotain kummallista. Seuraavassa kuvailemani ongelma ilmenee välillä, välillä taas ei.

Jos valitsen esim. ”Omaishoidontuen ohjeet muuttuvat 1.5.2017 alkaen” -otsikon oikealla hiirennapilla, ja valitsen kontekstivalikon ”Avaa uuteen välilehteen” -toiminnon, uuteen välilehteen avautuu etusivu, ei linkattu artikkeli. Bugi ilmenee myös, jos kopioin artikkelin linkin leikepöydälle (saman kontekstivalikon kautta) ja liimaan sitten tuon kopioidun osoitteen toisen välilehden osoitepalkkiin (välilehdellä avautuu artikkelin sijasta etusivu). Tämä hankaloittaa artikkeleiden jakamista.

Suoraan vasemmalla hiirennapilla avattuina linkit tuntuisivat toimivan kuten odottaisinkin (samalla välilehdellä avautuu siis otsikkoon linkitetty artikkeli).

Onnistuin toisintamaan bugin Firefoxilla (53.0) ja Chromella (58.0.3029.81), mutta tosiaan vain hetkittäin; välillä linkit toimivat myös kontekstivalikon kautta kuten pitääkin, eli otsikkoon linkitetty osoite viittaa artikkeliin eikä etusivulle.