Visual glitch in context menu during resizing after clicking URL |
||||||||
Issue descriptionSteps to reproduce the problem: 1. Enable new context menu 2. Open context menu for long link with graphic (it should have two tabs and link too long for displaying) 3. Click URL to expand / collapse it What is the expected behavior? Animation is smooth What went wrong? Animation is incorrect (for a moment menu options are displayed outside window above web page), please refer to video Did this work before? No Chrome version: 64.0.3277.0 Channel: canary OS Version: 7 Flash Version:
,
Nov 28 2017
,
Nov 28 2017
@marcin -- Thank You for the report. Tested the issue on Pixel XL (Android 8.0.0) and Pixel (Android 7.0.99) using Chrome Canary# 64.0.3278.7 and could not observe the issue. Could you please re-check on latest Canary and provide us the device details which would help us to triage the issue further. Thanks in Advance.
,
Nov 28 2017
Reported build (but on latest one from today it looks the same) and hardware details: Google Chrome 64.0.3277.0 (Official Build) canary (32-bit) Revision 64db0c41d5d476f76c9cb3d72fbc82e0f2a6d13e-refs/heads/master@{#519018} OS Android 7.0.0; SM-G930F Build/NRD90M Google Play services SDK=11200000; Installed=11746448; Access=1p JavaScript V8 6.4.365 User Agent Mozilla/5.0 (Linux; Android 7.0; SM-G930F Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3277.0 Mobile Safari/537.36 Command Line --use-mobile-user-agent --top-controls-show-threshold=0.5 --top-controls-hide-threshold=0.5 --use-mobile-user-agent --enable-pinch --enable-viewport --validate-input-event-stream --enable-longpress-drag-selection --touch-selection-strategy=direction --main-frame-resizes-are-orientation-changes --disable-composited-antialiasing --enable-dom-distiller --flag-switches-begin --enable-features=CustomContextMenu,ParallelDownloading --flag-switches-end Executable Path No such file or directory Profile Path /data/user/0/com.chrome.canary/app_chrome/Default Variations 45514eb0-77afc4fd 8b81f22b-f23d1dea c641c173-3f4a17df 6a89113b-f23d1dea 853359fa-3f4a17df 16e0dd70-3f4a17df da89714-4ad60575 9041608a-3f4a17df 1e528f0f-f23d1dea b130ecb8-1410f10 6025934e-3f4a17df d175604-2f393ff0 7e6cf017-3f4a17df 1949605e-ca7d8d80 45df7875-ca7d8d80 cf55e4c6-3f4a17df e9ee300f-cd19cd38 a0930725-3f4a17df d52c4ff7-d52c4ff7 3eb101d6-3f4a17df 236d5d9e-ca7d8d80 bd007046-3f4a17df 47e5d3db-3d47f4f4 77207729-e0e232cc f0a371b8-3f4a17df b1edbc38-cf4f6ead c3d1d2ca-3f4a17df 19c1fdaf-ca7d8d80 3042ad4b-f23d1dea 44c96c7b-ca7d8d80 57f575bb-f23d1dea 68812885-4d2fac87 b684f56f-122d152d 287f29ba-be7e4ff8 c561a755-f23d1dea e02508e8-3f4a17df e013e49e-4d5a0d36 937cad47-17606bad 9773d3bd-4fbbdb50 93731dca-f5f9e027 81328e71-f23d1dea 8e3b2dc5-93702590 9e5c75f1-b88f1793 b2972962-cead3f01 85663a5d-5c203355 f79cb77b-3d47f4f4 d1d8d202-97ae03d4 274c53f-f23d1dea 4ea303a6-95c3cf3c d92562a9-ca7d8d80 2b33233e-62e2c3f0 f66ea88e-4eb6d224 6973a1cf-3f4a17df 1aecb842-3f4a17df 4932440-f23d1dea 757a5d98-28165b59 65a86f01-ca7d8d80 30ab2dd8-cf4f6ead b2f0086-d3486be4 ef25c1eb-3f4a17df 2d871858-3f4a17df 344833e9-473e8c2e 4bc337ce-77afc4fd db5efd10-88e62167 9a2f4e5b-ca7d8d80 494d8760-5ce47ef8 3ac60855-486e2a9c 4442aae2-6e597ede ed1d377-e1cc0f14 75f0f0a0-a5822863 e7e71889-e1cc0f14 34baa302-f23d1dea f5fff3a2-f23d1dea 9cade933-fbb4ab19 493ac2c5-f23d1dea
,
Nov 28 2017
Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 29 2017
@marcin -- Thank You for the report. Tested the issue on Samsung Galaxy S7 (SM-G930F / Android 6.0.1) using Chrome Canary# 64.0.3279.0 and could not observe the issue. Could you please let us know if there is any specific flag enabled which would help in reproducing the issue. Thanks in Advance.
,
Nov 29 2017
I believe, that wrong behavior is visible in attached video in bug report (if not, please let me know). I believe also, that I have already provided all possible config info there too (there are variations showed, etc.) - if not please let me know Generally excluding enabling new context menu I don't remember any specific changes.
,
Nov 29 2017
Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 30 2017
Tested the issue in Android and could reproduce the issue. Steps Followed: 1. Enable new context menu 2. Open context menu for long link with graphic (it should have two tabs and link too long for displaying) 3. Click URL to expand / collapse it Chrome versions tested: 62.0.3202.84 / 64.0.3280.3 OS Android 7.0.99 / Android 8.0.0 Android Devices 7.0.99; Pixel PPR1.171120.001 8.0.0; Pixel XL OPR1.170623.027 This is a Non-Regression Issue observed when the flag "Enable new context" has been introduced. For screen cast and logs, please navigate to the below URL -- go/chrome-androidlogs/788954 Thank You.
,
Dec 27 2017
This is Clank UI issue, nothing to do with HTML <menu> implementation.
,
Feb 7 2018
Actually, in latest Canary it's enough to open new context menu with two tabs, switch from link to picture and back and expand/collapse link title/url field. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 Deleted