New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 918005 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

unable to downsize embedded element in google sites

Project Member Reported by marcore@chromium.org, Dec 27

Issue description

Chrome version: 70.0.3538.45
OS version: Windows 10
Case#:17756040

Description: user is unable to downsize the embedded element in google sites.

Steps to reproduce: 
create a new site on sites.google.com
add an embedded object (html example: https://drive.google.com/open?id=1MXLWYwAnE0xBiie3cAyiAxINz9_4a_JKaQVTuZsmg-0 )
result: https://drive.google.com/open?id=15a5oXIvFS2t8rtHlbwIhC1rFLpQFu20w

Current Behavior / Reproduction: 
you can only increase the size of the object

Expected Behavior: 
being able to decrease the size of the object

Last Good: 70.0.3538.44
First Bad: 70.0.3538.45
it's happening also on Linux 71.0.3578.98
https://chromium.googlesource.com/chromium/src/+log/70.0.3538.44..70.0.3538.45?pretty=fuller&n=10000

video of the issue:
https://drive.google.com/open?id=1GgZ5QcjxApCD-ZYjMaOa_OQ7oYHpNs9m

 
Components: Blink>HTML>Embed
Components: -Blink>HTML>Embed Blink
Cc: bokan@chromium.org
Hi David, it could be your commit
https://chromium.googlesource.com/chromium/src/+/9ef846bae155b8fac9416398c628d892b11c4487
could you please review ?
Cc: -bokan@chromium.org
Owner: bokan@chromium.org
Status: Assigned (was: Untriaged)
Thanks for the bisect. My CL is pretty unlikely to cause this kind of issue but nothing else in the range jumps out at me either. I'll take a closer look and see if I can find the right owner.
Cc: -marcore@chromium.org bokan@chromium.org
Labels: Needs-Feedback
Owner: marcore@chromium.org
I redid a bisect and got:

https://chromium.googlesource.com/chromium/src/+log/25304bc21625e4fb94ed283a4f6a9f2fa2ac4431..6187d94092a3ae876cfd6a6a70be23328a0a6bfd

Which is somewhere in 68 so quite different. Repeating the bisect around the good/bad points found above failed with both showing the issue. So it seems the bisect is unreliable and the issue appears somewhat arbitrarily.

Are we sure this is a Chrome issue and not an issue in sites.google.com? Another possibility is this is related to a Chrome experiment and we randomly enable it on each iteration of a bisect.

Sign in to add a comment