Chromium != Chrome

O

overmes2012-10-01 18:48:51

css

overmes, 2012-10-01 18:48:51

Chromium != Chrome

I checked my layout in different browsers and it turned out that the results in Chrome (21.0.1180.89m Windows 7) and Chromium (20.0.1132.47 Ubuntu 12.04 (144678)) are different:
Chrome

Chromium

Code (probably terrible)

<!DOCTYPE html>
<html>
<head>
    <title>HabraTest</title>
    <link href="/st/bootstrap/css/bootstrap.css" rel="stylesheet">
</head>
<body>
<table class="table table-hover row span4">
    <thead>
    <tr>
        <th>User Name</th>
        <th>counting</th>
        <th>results</th>
        <th></th>
        <th></th>
        <th></th>
    </tr>
    </thead>
    <tbody id="tbody">
        <tr><td>1</td><td>1</td><td>1</td><td>1</td><td>1</td><td>1</td></tr>
        <tr><td>1</td><td>1</td><td>1</td><td>1</td><td>1</td><td>1</td></tr>
        <tr><td>1</td><td>1</td><td>1</td><td>1</td><td>1</td><td>1</td></tr>
    </tbody>
</table>
</body>
</html>

You can check here the
problem is solved if you remove the row class from the table tag, probably it is not needed there, but all the same, browsers should be ready for this

. Why so? Or is this normal behavior and I'm just being picky?

Reply

Answer the question

In order to leave comments, you need to log in

1 answer(s)

S

Sergey, 2012-10-01
@overmes

1) Why do you need row? row is the container class for span*. span* - adds a float, thus knocking the element out of the flow. Open the debugger and see what's wrong.
And as for the differences - Firefox on Windows != Firefox on Linux, let alone different (be that as it may) browsers.