Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

[Bug] Pull to refresh triggered on full screen videos #16603

Closed
hkaancaliskan opened this issue Nov 16, 2020 · 10 comments
Closed

[Bug] Pull to refresh triggered on full screen videos #16603

hkaancaliskan opened this issue Nov 16, 2020 · 10 comments
Assignees
Labels
b:web-content Issues with websites. Check to see if the issue is GV or WebCompat too 🐞 bug Crashes, Something isn't working, .. Feature:Gesture Feature:Media

Comments

@hkaancaliskan
Copy link

hkaancaliskan commented Nov 16, 2020

Steps to reproduce

Open a video in full screen on any website (for me it's YouTube)
Swipe down to trigger pull to refresh

Expected behavior

Pull to refresh not triggered while on full screen.

Actual behavior

It's triggered on full screen.

Screenshot_20201116-194646_Firefox_Nightly

Device information

  • Android device: Xperia XZ1 Android 10
  • Fenix version: Nightly

┆Issue is synchronized with this Jira Task

@hkaancaliskan hkaancaliskan added the 🐞 bug Crashes, Something isn't working, .. label Nov 16, 2020
@github-actions github-actions bot added the needs:triage Issue needs triage label Nov 16, 2020
@hkaancaliskan hkaancaliskan changed the title [Bug] Pull to refresh works on full screen videos [Bug] Pull to refresh triggered on full screen videos Nov 16, 2020
@kbrosnan kbrosnan added b:web-content Issues with websites. Check to see if the issue is GV or WebCompat too Feature:Gesture Feature:Media and removed needs:triage Issue needs triage labels Nov 16, 2020
@rocketsroger rocketsroger self-assigned this Nov 16, 2020
@csadilek csadilek added this to ⏳ Sprint Backlog in A-C: Android Components Sprint Planning Nov 16, 2020
@Mugurell
Copy link
Contributor

I think in this case the solution would be to just add another check for fullscreen media to the canChildScrollUp method as the UNHANDLED result from PZC is the correct one.

@rocketsroger rocketsroger moved this from ⏳ Sprint Backlog to 🏃‍♀️ In Progress in A-C: Android Components Sprint Planning Nov 18, 2020
rocketsroger added a commit to rocketsroger/fenix that referenced this issue Nov 30, 2020
@rocketsroger rocketsroger moved this from 🏃‍♀️ In Progress to ⏳ Review/QA in A-C: Android Components Sprint Planning Dec 1, 2020
rocketsroger added a commit to rocketsroger/fenix that referenced this issue Dec 2, 2020
rocketsroger added a commit to rocketsroger/fenix that referenced this issue Dec 2, 2020
A-C: Android Components Sprint Planning automation moved this from ⏳ Review/QA to 🏁 Done Dec 2, 2020
@hkaancaliskan
Copy link
Author

@rocketsroger I've updated to 3/12 and its not working on youtube :(

@hkaancaliskan
Copy link
Author

@Mugurell issue closed but not fixed

@Mugurell
Copy link
Contributor

Mugurell commented Dec 7, 2020

I can also reproduce it on the latest Nightly.
Leaving to Roger to decide if this should be reopened or the work could continue on a new ticket.

@rocketsroger Seems like that check for HomeActivity.isImmersive is not being done at the right time.
Maybe we could could have a check to enable/disable pull to refresh in the fullscreenChanged method?

pkirakosyan pushed a commit to gexsi/user-agent-android that referenced this issue Dec 22, 2020
@rocketsroger rocketsroger reopened this Jan 5, 2021
@rocketsroger rocketsroger added this to 🏃‍♀️ In Progress in A-C: Android Components Sprint Planning Jan 5, 2021
@mawen7
Copy link
Contributor

mawen7 commented Jan 5, 2021

Can confirm the suggestion by @Mugurell works.
Can open a PR if you'd like @rocketsroger

@rocketsroger
Copy link
Contributor

I can reproduce as well. I think the reason that this sneaked passed my testing is that for some reason the first time pull to refresh is not disabled. After the first pull to refresh this then works correctly.

@rocketsroger
Copy link
Contributor

Maybe we could could have a check to enable/disable pull to refresh in the fullscreenChanged method?

I was hoping my solution is cleaner then keeping track in the fullscreenChanged method. I'll do some more investigation to see if I can salvage the isImmersive check. If not I think you're right that fullscreenChanged method is a good spot. Thanks,

@rocketsroger
Copy link
Contributor

Can confirm the suggestion by @Mugurell works.
Can open a PR if you'd like @rocketsroger

@mawen7 Thanks for offering your help. But I think since this is my mistake I should clean it up 😜

@mawen7
Copy link
Contributor

mawen7 commented Jan 5, 2021

Sure I understand that completely :)
Allow me one small hint: Since you can now use inFullScreen you can drop the isImmersive check.

IsImmersive was always false for me so I actually had to drop it.

@rocketsroger
Copy link
Contributor

rocketsroger commented Jan 5, 2021

IsImmersive was always false for me so I actually had to drop it.

That's interesting. For me isImmersive works except like it was mentioned the check was not called in fullscreen.

Allow me one small hint: Since you can now use inFullScreen you can drop the isImmersive check.

Yes, what I'm testing is to pass the inFullscreen into the check. I agree that since we're using fullscreenChanged we don't need isImmersive anymore. Thanks

rocketsroger added a commit to rocketsroger/fenix that referenced this issue Jan 5, 2021
A-C: Android Components Sprint Planning automation moved this from 🏃‍♀️ In Progress to 🏁 Done Jan 5, 2021
pkirakosyan pushed a commit to gexsi/user-agent-android that referenced this issue Aug 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
b:web-content Issues with websites. Check to see if the issue is GV or WebCompat too 🐞 bug Crashes, Something isn't working, .. Feature:Gesture Feature:Media
Projects
No open projects
Development

No branches or pull requests

5 participants