Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: r2697: cross-browser test needed on MacOS and *nix
ruud wrote:
Because whether or not Microsoft still supports something doesn’t really matter at all. Web developers don’t develop for Microsoft, they develop for visitors/users.
I agree that we do develop for visitors, but where do we draw the line? Will we still be developing for IE6 in 2010? I certainly hope not. Netscape 4 was essentially dead in 2003, six years after it was released. In terms of technology, six years is a long time. As you could probably tell, I don’t develop for IE6 any more. My clients are fine with it, since they, not their visitors, use TXP. Personally, I think we should bring the browser upgrade campaign back.
Obviously, the choice is up to you guys. I certainly don’t have a compelling argument other than it’s old and crappy. Unless Textpattern’s admin is recoded, it really doesn’t matter if IE6 is or is not supported.
Mac users shouldn’t have to upgrade (which is not free) to the MacOSX 10.4 to be able to use TXP. I doubt Safari 3 is available for older OSX versions.
Panther’s Safari was last updated to the Webkit of Safari 2. Tiger (released in 2005) is the oldest operating system Safari 3 supports. Based on a cursory glance of the Safari CSS reference, it looks like word-break is the only new CSS 2.1 property added. The rest appear to be -webkit- properties that have yet to be standardized. Basically, nothing new would affect Safari 2. If Textpattern used an extensive amount of JavaScript, then using Safari 3 as a baseline might be a problem because v3 fixed JS bugs and improved JS performance.
Offline
Re: r2697: cross-browser test needed on MacOS and *nix
jm wrote:
Panther’s Safari was last updated to the Webkit of Safari 2. Tiger (released in 2005) is the oldest operating system Safari 3 supports. Based on a cursory glance of the Safari CSS reference, it looks like
word-breakis the only new CSS 2.1 property added. The rest appear to be-webkit-properties that have yet to be standardized. Basically, nothing new would affect Safari 2. If Textpattern used an extensive amount of JavaScript, then using Safari 3 as a baseline might be a problem because v3 fixed JS bugs and improved JS performance.
Except for a truck load of bug fixes to the CSS parser and the overall handling of CSS properties. Except for a serious number of improvements to the HTML parser. I agree with you, no much new in Safari 3.0. Seriously. New features are only one part of upgrades to a rendering engine.
(except when you are MSiE where bug fixes are more like moving the hacks used by webdevelopers inside the source code of the browser to mask the bugs).
BTW where is the word-break property defined in CSS 2.1 ? Is it part of a not-yet-released CSS 2.1 draft ? (and it is not listed in the open issues with the CSS 2.1 CR.)
:-)
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline
Re: r2697: cross-browser test needed on MacOS and *nix
phiw13 wrote:
Except for a truck load of bug fixes to the CSS parser and the overall handling of CSS properties. Except for a serious number of improvements to the HTML parser. I agree with you, no much new in Safari 3.0. Seriously. New features are only one part of upgrades to a rendering engine.
You missed my point: Webkit’s1 additions are probably not going to be used by Textpattern. Developing TXP for Safari 3 will generally not have a negative effect on Safari 2. Safari 2 has excellent CSS support, so CSS bugs are less likely to be encountered than JavaScript ones. However, if a bug is encountered, not much can be done short of using either a CSS hack or browser sniffing, neither of which is appealing.
BTW where is the word-break property defined in CSS 2.1 ? Is it part of a not-yet-released CSS 2.1 draft ? (and it is not listed in the open issues with the CSS 2.1 CR.)
Sorry, I was thinking CSS 3, but obviously my fingers weren’t. Just a quick roundup of non-webkit- CSS 3 added to Safari 3:
word-breakoverflow-xoverflow-yresize
1 Webkit being the version shipped with Safari 3, not the latest nightlies.
Offline
Re: r2697: cross-browser test needed on MacOS and *nix
jm wrote:
You missed my point: Webkit’s1 additions are probably not going to be used by Textpattern.
I’m not talking about WebKit additions, but about plain old-fashioned bug fixes (e.g. bugs where Safari 2.0 was handling some properties wrongly).
Thinking ‘my site displays fine in Safari 3.0, thus it will work correctly in Safari 2.0.x’ is a sureproof road to problems.
Granted, with the current state of the TXP admin interface/stylesheet, it won’t make a big difference.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline
Re: r2697: cross-browser test needed on MacOS and *nix
FYI: I’ve been using Jon Hick’s admin reskin and it looks a little odd.
Offline
#18 2007-11-23 03:18:52
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: r2697: cross-browser test needed on MacOS and *nix
We don’t support hacks.
Offline
#19 2007-11-23 14:13:14
- els
- Moderator
- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: r2697: cross-browser test needed on MacOS and *nix
Do you still need a Linux test? I haven’t had time until now, but I could have a look at it this weekend.
Offline