Skip to content
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

Merged
merged 2 commits into from Aug 9, 2012

Conversation

gonchuki
Copy link
Contributor

@gonchuki gonchuki commented Aug 9, 2012

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).

…border.*Width is queried and that property is unset
@ibolmo
Copy link
Member

ibolmo commented Aug 9, 2012

Was there a failing spec? If not, we should have one that failed prior to the fix.

@gonchuki
Copy link
Contributor Author

gonchuki commented Aug 9, 2012

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.

@arian
Copy link
Member

arian commented Aug 9, 2012

1.4client would be fine. Now we have this fix, we can pull it in 1.4.6. (both #2325 and #2364 have the 1.4.6 milestone.. :))

@arian
Copy link
Member

arian commented Aug 9, 2012

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.

@ibolmo
Copy link
Member

ibolmo commented Aug 9, 2012

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 .

@gonchuki
Copy link
Contributor Author

gonchuki commented Aug 9, 2012

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:

should inherit the height from the child
Expected 'NaNpx' to equal '100px'.

should get a pixel based width
Expected 'NaNpx' to match /\d+px/.

should have a 0px border left
Expected 'medium' to equal '0px'.

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.

@arian
Copy link
Member

arian commented Aug 9, 2012

Looks awesome

...

merging...

@gonchuki
Copy link
Contributor Author

If you don't mind to merge again/cherry-pick (or manually edit), I acidentally left a trailing comma on the spec
gonchuki@7f59171

@arian
Copy link
Member

arian commented Aug 10, 2012

pulled

On Fri, Aug 10, 2012 at 4:43 PM, gonchuki notifications@github.com wrote:

If you don't mind to merge again/cherry-pick (or manually edit), I
acidentally left a trailing comma on the spec

gonchuki@7f59171


Reply to this email directly or view it on GitHubhttps://github.com//pull/2401#issuecomment-7646494.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants