Carrot2

Tabs clipped on Google Chrome with Ubuntu

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: 3.4.0
  • Component/s: Web Application
  • Labels:
    None

Description

The current search web form version (as of 14/05/2010) does not render correctly in Google Chrome.

Test environment:
Ubuntu 10.10
Google Chrome 5.0.396.0 dev

Activity

Hide
Dawid Weiss added a comment -

Weird, I have Ubuntu 10.10, Chrome 5.0.375.38 beta and everything looks fine. Looks like it's a font-related issue to me.

Show
Dawid Weiss added a comment - Weird, I have Ubuntu 10.10, Chrome 5.0.375.38 beta and everything looks fine. Looks like it's a font-related issue to me.
Hide
Dawid Weiss added a comment -

Oh, can you check with the trunk, please?
http://search.carrot2.org/head/search

There's been a recent fix to the CSS that might have fixed this.

Show
Dawid Weiss added a comment - Oh, can you check with the trunk, please? http://search.carrot2.org/head/search There's been a recent fix to the CSS that might have fixed this.
Hide
Maciej Bilas added a comment -

The result is the same.

CSS's font-family attribute of the element in question:
font-family: Tahoma, Arial, sans-serif;
If we were to follow the font issue trail then perhaps you either have the Tahoma font file (or don't have the MS Arial).
I find it quite unlikely to be the reason though, as firefox that has access to the same fonts renders the page as one might expect.

Show
Maciej Bilas added a comment - The result is the same. CSS's font-family attribute of the element in question: font-family: Tahoma, Arial, sans-serif; If we were to follow the font issue trail then perhaps you either have the Tahoma font file (or don't have the MS Arial). I find it quite unlikely to be the reason though, as firefox that has access to the same fonts renders the page as one might expect.
Hide
Maciej Bilas added a comment -

Tested with the current upstream version of Chrome in Ubuntu (6.0.401.1) and it's back to normal. Apparently it's Chrome's fault then.

Show
Maciej Bilas added a comment - Tested with the current upstream version of Chrome in Ubuntu (6.0.401.1) and it's back to normal. Apparently it's Chrome's fault then.
Hide
Dawid Weiss added a comment -

Sorry, I have Ubuntu 10.04 (LTS)...

Show
Dawid Weiss added a comment - Sorry, I have Ubuntu 10.04 (LTS)...
Hide
Dawid Weiss added a comment -

Don't know, we definitely need to check.

Show
Dawid Weiss added a comment - Don't know, we definitely need to check.
Hide
Maciej Bilas added a comment -

Good point, my bad. Ubuntu 10.04 LTS here as well. 10.10 got stuck in my head after reading an article about the recent UDS (Ubuntu Developer Summit) this morning.

Show
Maciej Bilas added a comment - Good point, my bad. Ubuntu 10.04 LTS here as well. 10.10 got stuck in my head after reading an article about the recent UDS (Ubuntu Developer Summit) this morning.
Hide
Maciej Bilas added a comment -

As said before: 6.0.401.1 fixes it.

Show
Maciej Bilas added a comment - As said before: 6.0.401.1 fixes it.
Hide
Dawid Weiss added a comment -

Seems like a CSS2 bug in Chrome.

Show
Dawid Weiss added a comment - Seems like a CSS2 bug in Chrome.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: