1575452 - Browser malfunction when u try to scroll in this website.

Status: RESOLVED DUPLICATE of bug 1423746

(Core :: Layout: Scrolling and Overflow, defect, P3)

Description

[Pranav bhattarai]

Attachment: Screencast from 08-21-2019 11:57:22 AM.webm

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

Steps to reproduce:

1. Use firefox 68.0.2 64 bit, in Ubuntu 19.04
2. Visit this website: https://source.android.com/devices/tech/dalvik/
3. Try to scroll down, but it won't let u.

(see the video for more details)

Actual results:

Flickering and not scrollable

Expected results:

Should have scrolled normally.

Comment 1

[Pranav bhattarai]

Just report this issue in Github: https://github.com/darkreader/darkreader/issues/1510

Comment 2

[Emilio Cobos Álvarez (:emilio)]

I can repro this if I set document.documentElement.style.filter = "invert(1)" for example.

That establishes a new containing block for fixed pos elements and the website seems to be doing something to figure out the position of the fixed menu that's breaking and restoring the position to the initial one.

I think bug 1423746 should fix it.

Comment 3

[Pranav bhattarai]

(In reply to Emilio Cobos Álvarez (:emilio) from comment #2)

I can repro this if I set document.documentElement.style.filter = "invert(1)" for example.

That establishes a new containing block for fixed pos elements and the website seems to be doing something to figure out the position of the fixed menu that's breaking and restoring the position to the initial one.

I think bug 1423746 should fix it.

There is an always a bug in Firefox, instead of adding features, devs should prioritize bug and bug-hunters.

Look how's Microsoft's Windows 10 update is being criticized, now their motto has changed.

I hope the same for firefox.

Comment 4

[Emilio Cobos Álvarez (:emilio)]

(In reply to Pranav bhattarai from comment #3)

There is an always a bug in Firefox, instead of adding features, devs should prioritize bug and bug-hunters.

If you would've bothered to read bug 1423746, you would've noticed that is a result of a long spec discussion where Firefox used to follow the spec but the spec was changed. So Firefox needs to catch up with the spec, yes, but it's not as black / white as you paint it.

Please be respectful, we're all here doing our best and aggressive comments lead to people spending time writing silly replies rather than working on Firefox :)

Comment 5

[Pranav bhattarai]

(In reply to Emilio Cobos Álvarez (:emilio) from comment #4)

(In reply to Pranav bhattarai from comment #3)

There is an always a bug in Firefox, instead of adding features, devs should prioritize bug and bug-hunters.

If you would've bothered to read bug 1423746, you would've noticed that is a result of a long spec discussion where Firefox used to follow the spec but the spec was changed. So Firefox needs to catch up with the spec, yes, but it's not as black / white as you paint it.

Please be respectful, we're all here doing our best and aggressive comments lead to people spending time writing silly replies rather than working on Firefox :)

Sorry if I am being disrespectful here. But I really want to use DarkReader extension, it goes good on eyes + saves my battery but there is always something new with the Firefox which is anti-Dark Reader.

What I want is a deadline when Firefox is fully compatible with firefox, not debates. Can I have one? This is every popular opensource extension in Chrome so, don't make u are Chrome for a smooth experience.

One more problem I often observe is while dragging a tab out of Firefox and again inserting it back to its place. This second action is not as BOLD as Chrome. Bold is the correct word for this.

Comment 6

[Emilio Cobos Álvarez (:emilio)]

There's no need to spam needinfos.

(In reply to Pranav bhattarai from comment #5)

Sorry if I am being disrespectful here. But I really want to use DarkReader extension, it goes good on eyes + saves my battery but there is always something new with the Firefox which is anti-Dark Reader.

Well, this extension sets a filter on the root element. That (per the old spec) causes all fixed elements to be contained in the root element's box, and it messes up this particular page which listens to scroll events.

You can see exactly the same kind of breakage if you do: document.documentElement.style.willChange = "transform" on Google Chrome.

So other than fixing bug 1423746 to update to the new spec (which is tracked there) there's not much to do. Is on the backlog of stuff to do, but it's not being "anti-dark reader".

What I want is a deadline when Firefox is fully compatible with firefox, not debates.

I don't understand this sentence.

This is every popular opensource extension in Chrome so, don't make u are Chrome for a smooth experience.

As I said this is an interaction between the site and some CSS the extension sets. The extension works better with the new spec. That's great and it'll work the same in Firefox once we update to the new spec.

One more problem I often observe is while dragging a tab out of Firefox and again inserting it back to its place. This second action is not as BOLD as Chrome. Bold is the correct word for this.

I don't understand what you mean by this, but I recommend to file a new bug in the right component: https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Tabbed%20Browser.

I'll dupe this to bug 1423746 since there's not much else than fixing that to do here.

Comment 7

[Pranav bhattarai]

(In reply to Emilio Cobos Álvarez (:emilio) from comment #6)

*** This bug has been marked as a duplicate of bug 1423746 ***

I hope this bug fixed by the end of this year.

There should be a feature that notifies the user who posted a bug report when they get solved. That would be really cool.

Comment 8

[Emilio Cobos Álvarez (:emilio)]

You can cc yourself in that bug, and it'll notify you of changes.