I really don't understand how Apple could release Safari 4 without
testing if Magnolia runs on it first! ;-)
The current situation is rather stupid, especially so since at
Magnolia, nearly the whole team works on Macs. Unfortunately, the
final release of Safari 4 did not fix the issues and we were already
releasing Magnolia 4.0, so we'll have to dig deeper now and come up
with a fix, and a 4.1.1 eventually. Patches & Pointers welcome, as
always!
http://jira.magnolia-cms.com/browse/MAGNOLIA-2654
http://jira.magnolia-cms.com/browse/MAGNOLIA-2216
- Boris
On Jun 16, 2009, at 11:51 AM, Will Scheidegger wrote:
Hi Tom
On 16.06.2009, at 09:47, Thomas Martin wrote:
So my question: has anyone had similar troubles with firefox on macs
yes
and maybe even a clue what's the nature or better the solution to it?
no
What I'm stuck with to get the work done: Firefox 2.
Now although I'm sure that one could find a workaround on the
Magnolia-side for this, I still think that these are browser bugs:
a) When a browser crashes when it reads HTML + JavaScript, then
there must be something wrong with it, don't you think?
b) When version 4 of a browser does not display certain content, but
version 3 did, then there must be something wrong with it, don't you
think?
-will
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
