#10797 closed defect (duplicate)
"Add a comment" box width is 1px with Chrome (works with Firefox)
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | 0.12.2 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
After upgrading to 0.12.2 from 0.11.7-4, the ticket comment box "Add a comment" appearance changed when using Chrome.
Attachments (1)
Change History (5)
by , 12 years ago
Attachment: | add-a-comment-screenshot.png added |
---|
comment:1 by , 12 years ago
follow-up: 3 comment:2 by , 12 years ago
Ah, of course, after forcing Chrome to reload the page, it seems to work now. Thanks. I wonder if there is a way to force the browser to reload the CSS from the server-side when it is changed..
comment:3 by , 12 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Replying to anonymous:
Ah, of course, after forcing Chrome to reload the page, it seems to work now. Thanks. I wonder if there is a way to force the browser to reload the CSS from the server-side when it is changed..
Oh yes, there are many ways ;-) See #9936.
If you don't mind, could you tell us:
- which version of Chrome / platform you were using?
- how were the .css files served? Directly from Apache / other web server, or tracd?
- what were the HTTP headers sent for the .css file?
comment:4 by , 12 years ago
Chrome is quite constantly biting me in the butt for my development sites that don't have cache-busters implemented. Usually TWO, and always at least two, Ctrl+Shift+R reloads sort things out.
Do you also see the problem there: http://trac.edgewall.org/demo-0.12/ticket/1 ?
It's very likely that Chrome didn't pick the new version of the CSS files, in your case.