Bug 87619

Summary: [EFL] Inner spin-button is not stylable
Product: WebKit Reporter: Alexander Shalamov <alexander.shalamov>
Component: WebKit EFLAssignee: Gyuyoung Kim <gyuyoung.kim>
Status: RESOLVED WONTFIX    
Severity: Normal CC: gyuyoung.kim, gyuyoung.kim, lucas.de.marchi, mcatanzaro, rakuco, sw0524.lee, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Description Alexander Shalamov 2012-05-27 23:08:46 PDT
Modifications of style -webkit-inner-spin-button doesn't affect style of a inner spin button inside input element, therefore,
layout test fast/forms/number/input-number-size.html is failing.
Comment 1 Gyuyoung Kim 2013-04-03 03:38:33 PDT
Created attachment 196317 [details]
Patch
Comment 2 Gyuyoung Kim 2013-04-03 03:44:02 PDT
It seems to me that EFL port starts to support number input type with a spin button. So, I think we just need to rebaseline for those cases. I don't know why -webkit-inner-spin-button is related to this bug.
Comment 3 Gyuyoung Kim 2013-04-03 05:02:54 PDT
Comment on attachment 196317 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=196317&action=review

> LayoutTests/platform/efl/fast/forms/number/number-size-expected.txt:33
> +FAIL numberWidth(0, 10, 1, "with-padding") should be 63. Was 47.

I understand what this bug title means. Let me check it further.
Comment 4 Gyuyoung Kim 2013-04-03 05:43:16 PDT
It looks I need to have time to find the clue. However, I think below three tests aren't related to this bug. Beside mac, qt and gtk also have own expected result for below. So, I will rebaseline those for EFL port.

fast/forms/number/number-appearance-rtl.html [ Failure ]
fast/forms/number/number-appearance-spinbutton-disabled-readonly.html [ Failure ]
fast/forms/number/number-appearance-spinbutton-layer.html [ Failure ]
Comment 5 Michael Catanzaro 2017-03-11 10:41:52 PST
Closing this bug because the EFL port has been removed from trunk.

If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.