Forum Replies Created
Thank you for the responses. There are definitely some better ways to think about this issue :)
You can build selectors to find the value of an attribute, but this wouldn’t be very useful here (ie: input[type=”text”]).
You can also use the :empty pseudo class on elements with no children (or text). Again, don’t think this is quite what you’re looking for (http://jsfiddle.net/fcSGR/)
You can learn more about selectors at the following two links if you’re interested.
Thanks @jasonkeene – No Mac here :(
I’m sure that’s a good resource for others though.
Does that still work? Everything I’m reading, including a friend who’s tested this on their iPad has reported that two finger scrolling no longer works for iframes. Thanks for the suggestion @arkson82
It really does seem that there is no simple solution for this. About ready to just set the height of the iframe to something like 10,000px for iPad users, and using a scrollable/hacked div just to get a fix out there. Really surprised this is difficult to pull off, and holding onto the hope that I’m just missing something.
You might need a different solution depending on what browsers you’re going to support, but the CSS3 box-shadow property is definitely worth taking a look at.
I don’t take any issue reading the content on this site.
@TheDoc makes a point that can be backed up by evidence… sort of. Many people do follow a principle of about 45-70 or so characters per line on the web, but it’s sort of debatable whether or not that figure is really the most ideal choice. While some “studies” suggest 45-70 characters is the ideal line length, other studies demonstrate that readers digest longer lines more quickly. There probably is some sort of ideal range, but it more likely has to do with other factors such as line-height/text size.
I’ve written just a bit on this here (point 3): http://www.uxbooth.com/blog/4-tips-and-tricks-for-more-legible-content/
Here are two supporting bits that offer contrasting data:
(There are several more free resources out there that I’ve stumbled across that also seem to suggest there isn’t really a magic number.)
If there is a really well done study out there on the subject, I’d love to see it! Most of what I’ve seen is pretty… flimsy.
The biggest problem I’ve faced when working on projects where our team uses a framework, is that the focus can sometimes shift to the framework instead of the goals we’re trying to accomplish by using the framework. It’s great if you can use a tool like a framework to facilitate processes, but important that your team draws some lines ensuring enough flexibility to get the job done.
I’d doubt there is one right answer.
On most of the projects I work on, we use a set of patterns and structures that help us stay consistent, but make very little use of any frameworks. We’ve tried deploying several in-house css/html frameworks with mediocre success, but ultimately we’ve found that we work better when starting almost entirely from scratch. At the same time, we follow some basic guiding principles that help us write legible code that is easy to revisit and modify if changes need to be made. We organize our documents so we can quickly find code that is related to one page, or sets of pages. We have a few basic patterns for what different types of pages should look like semantically.
It might be a bit more on the heavy side in the end, but we value our flexibility. Framework-less works for us, but might not be the best option for all teams.
What you are describing sort of sounds similar to how tables will size by default when given 100% width. It’s a little confusing to understand what exactly you are trying to accomplish, so some more details might help :)
To expand on that thought: you stated that you want column 1 to be determined by its contents, but column 2 to take up remaining space. How would that be different from column 2 being sized to its contents and column 1 taking up remaining space? An example of what you’re putting in both columns might be useful!
Anyways, my gut reaction is that something as simple as giving your table width: 100% will do the trick.
:) Two different solutions, good way to show that there is more than one answer.May 4, 2011 at 8:10 pm in reply to: Need help testing a pure CSS “Booth System” in IE9 #47280
Seems to be working properly in IE9 http://content.screencast.com/users/theleggett/folders/Snagit/media/1d4d84af-b002-4bd0-b52c-3c5a26ef402c/05.04.2011-20.09.38.png
There are no animated fade-ins.
There are absolutely multiple ways of doing this, but to start with a really basic example, let me direct your attention to this illustration:
One way to think about this is to split it into all the necessary visual pieces to create the effect. When you think about it, there are only two pieces to this style:
1. The box containing the content.
2. The graphic that gives (1) an appearance of wrapping around the “main content”.
Like Fourize said, this is just a matter of choosing the right colors and background images to create this style. You might choose any number of ways to accomplish this, here is one example:April 10, 2011 at 2:52 pm in reply to: So, what exactly to do about text-shadow for MSIE? #51655
Would offsetting the same text as a separate color behind the original text work? Not sure if there’s anyway to blur that text without the glow/dropshadow IE filters… which don’t function quite as nicely as the “text-shadow” property (http://www.howtocreate.co.uk/textshadow.html).
That works too, it’s just a bit more syntax heavy. As far as I’m concerned though, if that’s a style you need, and that’s the only way you can implement is in all the browsers you’re designing for, it’s a good solution.