LDraw.org Discussion Forums

Full Version: I think links should look different than plain underlined text
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4
Try looking at the page with SRWare Iron (a de-googled Chrome branch)
http://www.srware.net/en/software_srware...wnload.php
, choose "inspect element" there.
Their DOM inspector is simply marvellous and just better than everything I've seen in Firefox.
You know that iron is really just normal chrome with a small patch to hardcode some settings and change the name everywhere, right?

And, at this point, its set of "developer tools" is lagging behind chrome's.

EDIT: Oh, another place the link color still needs to be changed is in the post preview.

EDIT 2: More about the questionable nature of iron can be read on its wikipedia talk page.

EDIT 3: I too have always been rather suspicious of google (If information is power, why aren't they ruling the world yet?), I use GoogleSharing and when that is unavailable, I try to stick to using scroogle. When you turn off all the fancy url bar stuff and turn off the "anonymous" statistics reporting and disable flash and whatnot, chrome is actually relatively safe to use (although I'm certainly not a fan of its secret auto-updating). Still, my favorite browser is xxxterm, I even submitted a patch for its "favorites" code it in its earlier stages.
You may need to add !important to them.

Many site and forum software use id="" instead of class="" to label things. Which in CSS means that they become top of the list (in most browsers) behind only style="". But adding !important to an element will override cascading unless another !important is encountered. I nearly ripped my hair out recently before discovering this trick.

Tim
I'll have to read more about the "Iron is a scam" claim,
but up to now I did not think that: Here's a list of things which Iron claims to have removed from Chromium:
http://www.srware.net/en/software_srware...s_iron.php
Since the sourcecode can be downloaded, you can verify that the changes are there.
Your article puts that into a different light, I'll read it.
Let's cancel the "Iron vs Chrome" discussion here, as it is off-topic, and I do have to read more about the "scam claim"
before I could continue. Looking at the number of posts in this thread, it is a little funny to me how
a question like "can we please have underlined hyperlinks?" can lead to such a big thread :-D
I use both Chrome and Firefox with Firebug. Both aren't showing me anything useful but I will try Tim's suggestion with the important tag to see if that works.
That didn't work. Looking into this some more.
Looking at it in Chrome's inspector, the underline isn't present in the image element itself at all, but only in the parent A element. The underline appears to be underlining the nonexistent text portion of the A element.
I was thinking the same thing. I guess I'll just have to class all linked imgs.
I think it's interesting to note that IE 9, Firefox 9, and Chrome 16 all render the lines differently. Firefox places them at a position that would be underneath text, if text were present along with the image. Chrome puts them above the image. IE puts them above the image, but then erases one text line's worth of space above the line (see the info links on the left of all the Announcements entries on the main page).

I'm not much of a CSS expert, but this seems to indicate that whatever is being used to get the lines in the first place, it's something that just about nobody else is doing, because if it were common, I can't see having completely different rendering on the three top browsers.
Hi Travis,

I've done a fair bit of research into CSS and good UI design. I'm certainly no expert but I have looked up the theory of how it should work and now have a pretty good idea of common problems.

The underline trick should work as a standard and does work on many sites. It's definitely valid CSS with a standardised(ish) behaviour (border behaviour is pretty standardised with the exception of whether they're considered 'inside' space or 'outside' space). The problem here is that much of the forum uses pointless CSS trickery all over the place to, I assume, ensure each little bit looks identical on many browsers. And of course each module is written by a different author who uses their own different tricks, so there's not even a nice standard way to fix the problem.

For example the images next to the announcements aren't 'img' tags. They're simply 'a' links set with a background image and presumably a fixed size. What is worse is that they are inheriting this behaviour from the table they're contained in which makes debugging them hard.

Unfortunately there's little we could do about this aside from a) overriding each problem bit individually and hoping it works or b) abandoning the dots and going back to regular underlining.

Tim
Pages: 1 2 3 4