Bug 118938 – CSS transforms do not apply to the options of a selectbox

• Status: RESOLVED
• Resolution: WORKSFORME
• Component: CSS

[satya]

Created attachment 207186 [details]
Test file

When there is transform applied, the drop-down will not honor the scale.
Use the attached transTest.htm to reproduce the page.
Steps:
1. Find the attached transTest.htm
2. Open in Chrome
3. Click on the select box to open the drop-down
Dorpdown is bigger than the select box

Expected result: Dropdown should be of same width to that of select box

[Santosh Mahto]

Created attachment 207325 [details]
Patch

[Santosh Mahto]

I dont see any reason we should ignore css transform while calculating the size 
of popup.
So Adjusted the code.

[Simon Fraser (smfr)]

Comment on attachment 207325 [details]
Patch

Needs a testcase. What does this mean for popup menus?

[Santosh Mahto]

(In reply to comment #3)
> (From update of attachment 207325 [details])
> Needs a testcase. What does this mean for popup menus?
In normal case we expect: popup menu width ==  select element width.
But when we change the width (e.g by scaling) of select element by css transform 
then popup menu width is not changed and it remains to be original width
so with transformed applied popup menu width !=  select element width. 

I found difficulty in creating testcase covering size of popup menu.
could you suggest already present popupmenu testcase
.

[Santosh Mahto]

(In reply to comment #3)
> (From update of attachment 207325 [details])
> Needs a testcase. What does this mean for popup menus?
In normal case we expect: popup menu width ==  select element width.
But when we change the width (e.g by scaling) of select element by css transform 
then popup menu width is not changed and it remains to be original width
so with transformed applied popup menu width !=  select element width. 

I found difficulty in creating testcase covering size of popup menu.
could you suggest already present popupmenu testcase.

[Santosh Mahto]

it seems bug #66062  and this address same issue.
Details Discussion is there about effect:
https://bugs.webkit.org/show_bug.cgi?id=66062

[Santosh Mahto]

May I know why current code is
IntRect absBounds = absoluteBoundingBoxRectIgnoringTransforms();

and you updated patch with
https://bugs.webkit.org/show_bug.cgi?id=15678
 IntRect absBounds = absoluteBoundingBoxRect();

[Brent Fulgham]

Safari, Chrome, and Firefox all agree on rendering for this test case. I don't believe there is any remaining compatibility issue.