Closed GoogleCodeExporter closed 9 years ago
I can confirm this on 11.0.696.28 beta. Strange is - it behaves correctly on
localhost, but incorrectly on a domain. Maybe a browser issue with javascript
executing privileges?
BTW: works with chrome stable (10.x)
Original comment by p...@praus.net
on 3 Apr 2011 at 9:09
I can confirm the same behavior on 12.0.725.0. I am seeing the issue with
localhost, though.
Original comment by bradford...@gmail.com
on 10 Apr 2011 at 7:51
Attachments:
@bradford ... thanks for the screenshot with firebug enabled.
I just tried with the latest beta of google chrome and I´m not able to
reproduce the behaviour.
a couple of things you could try to help solve this issue:
– delete cache, browser-history, auth, cookies, ...
– try remove the js from base.html (either all or one after another) and see
if the problem still exists.
regards,
patrick
Original comment by sehmaschine
on 11 Apr 2011 at 8:06
I've been having this problem for a while with Grappelli. It finally got
annoying enough to come look for a bug report. I'm using v2.2 right now with
Django 1.2. Only happens with Chrome (different versions on different
machines).
Will be attempting an upgrade to 2.3 and Django 1.3 today and will debug
further once I get that done.
Original comment by webri...@gmail.com
on 15 Apr 2011 at 2:07
Ok...I've been testing and here is what I've found:
Chrome 10.X from Ubuntu 10.10, Windows XP/7 and OSX does not produce the issue.
Chrome 11.0 from the developer channel in Windows does produce the issue.
Chrome 12.x from Chromium daily PPA produces the problem consistently in Ubuntu
10.10.
I didn't want to mess with my OSX env and not sure how to get 12 on windows
(nor do I really care as it has the issue in 11).
I did try to disable ALL JS on the page and the problem persists. I'm taking a
guess that it's something to do with the way Chrome renders the page (not a JS
issue), and it doesn't seem to be an issue right now but might be in the next
couple months as the new versions of Chrome are released.
Anything else I can test please let me know!
Original comment by supp...@sezlik.com
on 21 Apr 2011 at 5:43
awesome, thanks.
you could try what axel described in a similar ticket.
structures.css, line 438: please try to modify all parameters, especially the
float. Maybe add a display: block;
.container-flexible {
clear: both;
float: none;
height: 100%;
position: relative;
width: auto;
}
Original comment by sehmaschine
on 22 Apr 2011 at 8:43
messed around with .container-flexible and .container-grid and it didn't seem
to make any difference.
Original comment by webri...@gmail.com
on 22 Apr 2011 at 11:37
Same thing here:
- Grappelli 2.3
- Chrome 12.0.725.0 dev
- Ubuntu 10.10
Works fine on Chrome "10.0.648.204"
Original comment by yerfino...@gmail.com
on 25 Apr 2011 at 5:34
I have the same problem.
Mac OS X 10.6.7
Chrome 11.0.696.57
Original comment by m...@kvove.ru
on 29 Apr 2011 at 9:13
solved with r1430
Original comment by parsch.inc@gmail.com
on 3 May 2011 at 5:17
problem was located in components css, line 31:
chrome has a problem with css3 pseudo-class :empty
Original comment by parsch.inc@gmail.com
on 3 May 2011 at 5:19
Works great now, thanks!
Original comment by yerfino...@gmail.com
on 3 May 2011 at 5:29
Awesome! Thanks a bunch! Works great!
Original comment by webri...@gmail.com
on 4 May 2011 at 8:33
It seems that the ul.tools element ("Add OBJECT", "History", "View on page") is
still not showing unless you click on the page.
Original comment by m...@jacobian.se
on 5 May 2011 at 5:01
[deleted comment]
Replace line 21 in tools.css 'display:none;' with
padding: 0;
height: 0;
border: 0;
visibility: hidden;
and "History" will show at start.Works for me.
Original comment by mdpopov...@gmail.com
on 10 May 2011 at 3:09
Guys,
I followed every suggestion from this thread but still have the problem with
chrome 11 on OSX.
Any ideas what I can check/test/change?
Thanks, Arshavski Alexander.
Original comment by alexar...@gmail.com
on 24 May 2011 at 9:16
r1432: all ":empty" declarations in the stylesheets are commented out by now
(as we should avoid delivering empty elements anyway).
@arshavski: as there are no more styles for empty elements everything should be
shown immediately (tested it with chrome 11.0.696.71 on osx)
Original comment by parsch.inc@gmail.com
on 25 May 2011 at 7:40
I just downloaded the latest version from the trunk, deleted browsing data and
still have the same problem.
What am I doing wrong?
Thanks, Arshavski Alexander.
Original comment by alexar...@gmail.com
on 25 May 2011 at 2:39
I have the same problem. Grappelli from pypi, chrome 12.0.742.68 beta. But it
always happens, not randomly.
Original comment by kai.kue...@gmail.com
on 5 Jun 2011 at 3:08
@kai, arshavski: the grappelli-version 2.3.2 (on pypi and on google-code) still
contains the old css (we are trying to release a new version soon). you can
wait for a new package or just use a svn-checkout.
Original comment by parsch.inc@gmail.com
on 6 Jun 2011 at 7:05
Running from svn. I experience this problem consistently when in a form that
has non field specific errors. For example with unique_together validation
errors the admin edit page will show an error at the top. It will say "Please
correct the error below." but not actually show the errors until I click
anywhere. This is the only place I see the problem after updating to svn.
Original comment by dbu...@cristoreyny.org
on 8 Jun 2011 at 2:49
Original issue reported on code.google.com by
razvan.savu
on 26 Mar 2011 at 9:17Attachments: