Closed (fixed)
Project:
Drupal core
Version:
8.4.x-dev
Component:
settings_tray.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
22 Jun 2017 at 03:49 UTC
Updated:
30 Aug 2017 at 20:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
tedbowOk here is patch that just makes a use of the tray that has long string where you would need to scroll to get to the bottom.
No I don't think the problem is a table or anything to do with the menu forms.
This happens in this test also.
Basically when trying to scroll to the bottom of the tray it will also scroll the body and "pop" you back to a little before the bottom of the tray.
This happens until the bottom of the main page is reached also. Then it will not "pop" back in the tray.
Here is video that demonstrates this https://youtu.be/eTNTgpMuGiA
Comment #3
tedbowUpdating title because it doesn't just happen with Menu form
Comment #4
tim.plunkettFrom my interaction with settings tray, I'd almost call this major. It is very frustrating 😅
Comment #5
GrandmaGlassesRopeMan- Fixes an issue with long forms having their scroll percentage reset after 100% scroll was reached and the scroll event was bubbled up to the parent.
Comment #6
GrandmaGlassesRopeManBroken behavior,
Fixed behavior,
Comment #7
tedbow@drpal thanks for the fix. I have tested this out manually and it fixes the problem for me.
I have looked into how we might test this and I don't think this is something our Javascript testing .
The only related function I found was \Zumba\GastonJS\Browser\BrowserMouseEventTrait::scrollTo but this only deals with the "page" and doesn't deal individual elements.
I think this could get committed without a Javascript test because is well documented in this issue how to reproduced the error manually. Especially considering what much more important things in Drupal core have no JS functional testing at all.
Comment #9
webchickThanks so much for those moving GIFs; SO HELPFUL in figuring out what bug is being fixed!
Committed and pushed to 8.4.x. Looks like it could use a backport to 8.3.x too at some point, if someone has time (there are es6 hunks in here so I don't think it will apply). Tagging as novice, since it seems like this fix would be pretty straight-forward to backport.
Comment #10
wim leers8.3.x is closed now, so we can close this issue, since it won't be backported to 8.3.x anymore.
Comment #12
tedbowChanging to new settings_tray.module component. @drpal thanks for script help! :)