[MAGNOLIA-2778] Google Chrome fails to render magnolia admincentral properly Created: 10/Jun/09  Updated: 23/Jan/13  Resolved: 22/Jun/09

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: None
Fix Version/s: 3.6.6, 4.0.2, 4.1.1

Type: Improvement Priority: Minor
Reporter: Rob van der Linden Vooren Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: gui, layout
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File in-chrome.jpg    
Issue Links:
relation
is related to MAGNOLIA-2654 Can't render trees and lists with Saf... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Viewing Magnolia AdminCentral with Google Chrome browser (v 2.0.172.31), elements that should render are not rendered;
For example, the node tree under 'Template Definitions'.



 Comments   
Comment by Magnolia International [ 10/Jun/09 ]

If no tree at all is rendered (website, dms, ...), this is possibly the same issue as with Safari 4 - after all, both use WebKit.
See MAGNOLIA-2654

For the record:
http://www.useragentstring.com/pages/Chrome/
http://www.useragentstring.com/pages/Safari/ – looks like Chrome and Safari 4 both use the same (or very close) version of WebKit.

Comment by Magnolia International [ 22/Jun/09 ]

fixed by MAGNOLIA-2654

Generated at Mon Feb 12 03:40:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.