if (navigator.userAgent.indexOf(“Firefox”) != -1) {
$(“.yui-content div[class*='ellipsis']“).ellipsis();
}

Any idea to increase performance there are more div’s

IE8 also implements the entirety of CSS 2.1, which no other browser out there does. I like the attitude of trying to get the basics right before implementing experimental functionality like canvas or css transformations.

Wake me up when IE is comparable in terms of capability and performance with, hell, Firefox 2.

As far as implementing it in Javascript preventing proper copy/paste into Excel, I think it depends on the implementation. Sure, you may get ellipsises here and there, but it’s simple enough to just find/replace those.

And yes, I think the style should be implemented in Gecko. But as far as importance goes, while I’d love to see it, I don’t think its absence is harming uptake for Firefox at all.

Gmail probably removed it because of RTL issues, which were pretty severe on opera when I tried it (opera 9.5).

I’m not a big fan of implementing this in javascript, especially in grids, because aside from the performance issues when resizing this also makes it difficult to copy/paste the grid in its entirety to excel. There are quite a few users that actually do that last bit.

I’m not sure what part of my comment you’re responding to, if any, but I’ll bite. I’m not convinced it’s a usability issue. An ellipsis is pretty well understood by most people to indicate truncation. And in any case, its use should be paired with functionality to make the rest of the text available, either in tooltip form or in some form of DHTML expansion functionality (using your example, it should only be applied if Javascript is available, and paired with the ability to resize columns).

@andysky,

You didn’t get my point — Websites which look fine in IE (by webmasters who didn’t test on Firefox) with the text-overflow CSS property, won’t display properly on Firefox — this damages Firefox’s image for even a *new user* who’s trying this browser and visits such a site.

To some small degree, perhaps, but with obviously cut off text, the ellipsis is primarily a style concern. I doubt it will leave a lasting impression for most users.

To further reinforce my point, now imagine that that user then tries Google Chrome and the site displays perfectly. Which browser will this user, in the end, choose?

See what I mean?

In the case where the difference is an ellipsis or no ellipsis? I doubt it would affect browser choice. But if it does, so be it. That’s part of the benefit of browser choice. And if it drives a user to Chrome or Safari, I’m glad. WebKit is stronger than Gecko anyway, and I’d prefer Chrome and Safari replace Firefox in the market for the foreseeable future. If it drives a user to IE? Oh well. It’s a drop in the bucket compared to IE’s market share trend.

It’s such a tiny, insignificant issue. I really doubt most users even notice. I mean, for instance, even as a UI developer with strong design skills, I don’t know how long Gmail had lost its text-overflow goodness (in Safari, I don’t know whether it’s still there in other browsers) before I noticed. And granted, I was disappointed to see it go, but only from an aesthetic perspective. Gmail is no less usable, and I can’t imagine switching browsers to get some ellipsis action. And I run multiple browsers! Getting a regular user to switch browsers is very difficult, and this is really unlikely to be the straw that breaks that back.

I am working on some of the other issues!
Devon

See what I mean?

You didn’t get my point — Websites which look fine in IE (by webmasters who didn’t test on Firefox) with the text-overflow CSS property, won’t display properly on Firefox — this damages Firefox’s image for even a *new user* who’s trying this browser and visits such a site.


...
var s = document.documentElement.style;
if (!('textOverflow' in s || 'OTextOverflow' in s)) {
// implement workaround
}
...