Bug 13519 - Zoom control is laid out below MapQuest map instead of next to it at hilton.com
Summary: Zoom control is laid out below MapQuest map instead of next to it at hilton.com
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL: http://www1.hilton.com/en_US/hi/hotel...
Keywords: HasReduction
Depends on:
Blocks:
 
Reported: 2007-04-27 01:33 PDT by mitz
Modified: 2016-09-15 10:45 PDT (History)
2 users (show)

See Also:


Attachments
Test case/reduction (well, it's not really a reduction, but a test case of one). (521 bytes, text/html)
2009-04-21 12:11 PDT, Sam Sneddon [:gsnedders]
no flags Details
A better test case that tests both padding and border. It also simplifies the pass condition. (490 bytes, text/html)
2009-05-14 13:38 PDT, Sam Sneddon [:gsnedders]
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description mitz 2007-04-27 01:33:20 PDT
On the URL, there is a map and a vertical zoom selector. The zoom control should be next to the map on the right. Instead, it appears below the map on the right. Layout in Firefox is correct.

Regression:
Don't know yet. The page hangs Safari 2.0.
Comment 1 Sam Sneddon [:gsnedders] 2009-04-21 12:11:06 PDT
Created attachment 29660 [details]
Test case/reduction (well, it's not really a reduction, but a test case of one).

It appears for display:table the 'width' property isn't the content width: the content width is 'width' - 'border-left'/'border-right' in this test case. Probably ought to check the entire box-model with an element which has display:table.
Comment 2 Sam Sneddon [:gsnedders] 2009-05-14 13:34:33 PDT
Padding appears to equally reduce the width.
Comment 3 Sam Sneddon [:gsnedders] 2009-05-14 13:38:09 PDT
Created attachment 30354 [details]
A better test case that tests both padding and border. It also simplifies the pass condition.
Comment 4 Sam Sneddon [:gsnedders] 2016-09-15 10:45:29 PDT
This appears to have got fixed in the intervening years.