New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix for #2325 and #2364 (should also fix -more #1125) #2401
Conversation
…border.*Width is queried and that property is unset
Was there a failing spec? If not, we should have one that failed prior to the fix. |
No failing spec but I can make one. Just not sure if this should go in 1.4client folder or create a 1.5 one. |
Basically copy those two jsfiddles in the specs.. update it a bit.. check if it fails without the fix.. and verify it passes with the fix. |
Right, and just try to run the specs against most browsers. I'm sure the rest of the team can cover any missing browsers before release. Thanks @gonchuki . |
I ended up creating my own specs as I wanted to test for all three failing properties (border.*Width was the culprit but it bubbled up to width/height to produce the NaNpx error) for reference, this is the result of the failing specs:
my IE is not working right with the test suite so I couldn't run it, but unless these specs uncover new bugs the changed code was already IE-only so there's nothing new there. |
If you don't mind to merge again/cherry-pick (or manually edit), I acidentally left a trailing comma on the spec |
pulled On Fri, Aug 10, 2012 at 4:43 PM, gonchuki notifications@github.com wrote:
|
remove Browser.ie check as Opera also returns non-numeric value when border.*Width is queried and that property is unset.
The fact that Opera returns "medium" when the border is unset must not be interpreted as 3px as suggested in #2364 since that string is actually a quirk from the browser (the border is actually 0px, Dragonfly properly shows this property as being unset in the layout pane).