Bug 94989
| Summary: | Media query for unfloating causes unusual stacking behaviour | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Justin Martin <signup> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Minor | CC: | ahmad.saleem792, karlcow, ntim, thmichel |
| Priority: | P3 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | http://thefrozenfire.com/data/webkit-bug/ | ||
Justin Martin
A demo of this bug is available at http://thefrozenfire.com/data/webkit-bug/. I'm unsure what exactly is happening in this instance, but a few people have been able to reproduce, including in FireFox.
When using a media query to un-float a div which is set to inline-block display, the return to being floated has it stacked below its usual position.
Chromium 18.0.1025.168 (Developer Build 134367) Ubuntu 12.04
OS Linux
WebKit 535.19 (trunk@106313)
JavaScript V8 3.8.9.19
Flash 11.2 r202
User Agent Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.168 Chrome/18.0.1025.168 Safari/535.19
Command Line /usr/lib/chromium-browser/chromium-browser --flag-switches-begin --disable-webgl --enable-smooth-scrolling --enable-experimental-extension-apis --enable-sync-tabs --flag-switches-end
Executable Path /usr/lib/chromium-browser/chromium-browser
Profile Path /home/justin/.config/chromium/Default
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Thierry Michel
Almost the same here : http://thierrymichel.net/test/webkit-bug/
1. Open the link with a wide window (> 600px).
-> float with media queries is correctly applied
2. Resize the window (< 600px)
-> float is correctly remove (no media queries applied)
3. Resize again (> 600px)
-> float is different from the first rendering !!!
Tested
- on Max OS X 10.5.8 / Windows 7
- on chrome 29.0.1547.76, 32.0.1658.2 canary, safari 6.0.5 (8536.30.1) / chrome 29...
Works correctly with IE9, Firefox and Opera...
tm
Ahmad Saleem
I am not able to reproduce this bug using following test case in STP176 and WebKit ToT and seems to match Chrome Canary 118.
@Tim & @Karl - any help?
Test URL: https://thierrymichel.net/test/webkit-bug/
Karl Dubost
Ahmad,
Yes this is working as expected now.
Thanks for the heads up.