PUBLIC MARKS with search fixed-unitinvestmenttrust

See what I mean? Can you see IT? The 1 is off center. Instead of being optically centered, it's geometrically centered. So it just looks wrong. Really, what happened there, Steve? Where did all that love for typography and attention to detail go?

Ça n'a jamais été de l'amour, juste un facteur différentiateur.

PATCH-444, Make Twitter hashtags visible. Twitter does some script magic and ends up with broken element nesting: <span><strong>foo</span></strong> in turn causing Opera's layout engine to be upset. This will be fixed with the new parser so we'll just patch it meanwhile.

In this article, we'll discuss the basic pros and cons of each type of layout, and why flexible layouts, despite past drawbacks, will be gaining a competitive edge in the next several years over the once popular fixed-width choice.

What happens when the user zooms? The Nokia N8 removes the fixed element entirely; and we can all agree that’s not the best possible behaviour. But what should happen? I have no clue. Browsers can’t handle the situation, and the spec is silent.

For this project, I have a page template with several container elements that all have a 1 pixel by 1 pixel PNG background set to repeat, and it looks great when testing it in IE 7 and IE 8. So, I created my next page template with the same styling. This time, IE 7 and 8 both choked when handling the background-repeat. Instead of repeating, both of these browsers inexplicably tried to stretch the 1×1 image across the entire container. The PNG happened to have 60 percent alpha transparency, but I’m not sure that matters. A coworker suggested making it a 10×10 pixel image instead, just to see what happens. Surprise, surprise. That fixed it.

Oct 04, 2010

karlpro said...

HTTP gives you a way to handle the right user (agent) interaction. In the discussion there is a missing piece above. What is the URI? The HTTP code will give information about a URI and its evolution in time. For a user agent, is it a fixed one or temporary one? I'm surprised you didn't use a 307 Temporary Redirect. The information accessible at this URI is not accessible anymore, you can send the client to another URI with with an Expire field, with the information that the client has reached its limits and should retry the original URI in xxxx minutes. What is happening on the server side, machine limits, disks, etc. is *not* important and not part of the exchange of messages. Think about what is useful for going to the next meaningful interactions in terms of messaging (for a human or a software).Note also that HTTP WG is at work to define HTTPbis and it is the right time to have contributions of people who have real implementations issues. I would encourage you to send an email to the HTTP Working Group at ietf-http-wg@w3.org with the link to this blog post and an introduction.The draft documents are available at http://tools.ietf.org/wg/httpbis/