Heroes never die, they just reload
The Principles Of Cross-Browser CSS Coding
Advertisement It is arguable that there is no goal in web design more satisfying than getting a beautiful and intuitive design to look exactly the same in every currently-used browser. Unfortunately, that goal is generally agreed to be almost impossible to attain. While I agree that creating a consistent experience for every user in every browser (putting aside mobile platforms for the moment) is never going to happen for every project, I believe a near-exact cross-browser experience is attainable in many cases. In this article, I’ll be describing what I believe are some of the most important CSS principles and tips that can help both new and experienced front-end developers achieve as close to a consistent cross-browser experience as possible, with as little CSS code as possible. Understand the CSS Box Model This is one of the first things you should be thoroughly familiar with if you want to be able to achieve cross-browser layouts with very few hacks and workarounds. Use a CSS Reset
Free CSS Drop-Down Menu Framework - LWIS.NET
Description Free CSS Drop-Down Menu Framework was first released back in June, 2008. Since then it has struck the audiences with its perfect cross browser performance and wide variety of drop-down menu transformations and themes. As the internet changes this project remains a steady advocate of purely CSS driven solutions. Modular, with themes. Not only HTML is separated from CSS, but even CSS definitions are categorized into structural and thematic types. Frequently Asked Questions Q.Why are you using CSS property visibility and not display in order to reveal and hide drop-down menus? In my tests some versions of IE7 did not handle display property correctly. Now you will be able to manipulate your drop-downs with JavaScript (use animations, etc.). Q.How do I center the menu horizontally? There is no reliable cross browser solution to center those floating menu items. Please refer to the two available demo templates illustrating horizontal menu centering - MTV.com and Adobe themes. Q. A.
| , | TopCareer.ru
Если вкратце, то суть такова: в России работают на результат, в Зеландии на процесс. Огромную разницу между этими двумя подходами я почувствовал на себе, устроившись в небольшую, но активно развивающуюся веб-компанию Rad3.com. Время было кризисное, с работой не очень хорошо, поэтому сразу меня на постоянную позицию не взяли. Одно из важнейших здесь понятий — уверенность в завтрашнем дне. Как-то так получается, что с детства гражданам вбивают в головы — нет ничего хуже нестабильности. Недобросовестного Афоню очень сложно выгнать. Всех этих сложностей можно избежать, если Афоню сократить, официально удалив его должность из реестра. Закончив отступление, подчеркну, что постоянная работа — это стабильность и не больше 10% зарплатного прироста в год. В Новой Зеландии тема денег — табу. Общая практика такова, что даже в крупных компаниях вроде Телекома два человека, занимающих одну позицию, могут получать по-разному. Деньги не должны и не могут быть стимулом, как считают киви.
iOS has a :hover problem
Posted at July 5, 2012 01:33 pm by Nicholas C. Zakas Tags: CSS, Hover, iOS, Mobile Recently, I got my first iPad. I’ve had an iPhone since last year, and had gotten used to viewing the mobile specific view of most websites. When I got the iPad, it was my first time experiencing desktop webpages using a touch interface. :hover exists everywhere One of the things we’ve been told and I’ve repeated over and over again is that touch devices have no concept of hover. Naturally, with a touch device, there really isn’t a lingering pointer. So it goes without saying that most developers expect touch devices to simply ignore CSS rules containing :hover. This is where the people at Apple might have been a bit too smart. No double taps When I started experiencing the double tap behavior, I was noticing what appeared to be a hover state being shown after the first. My first step was to create a simple example to see if I could reproduce it. Double tap! Possible workarounds if (! Conclusion References
960 Grid System
amp;mdash; What problems does Google Wavesolve?
There are countless pundits and other tech gurus describing Google Wave as a disappointment, lately. Most of that seems to come from the fact that nobody seems to get what Wave is for. So they compare it to social media. Is Wave the next Twitter? Nope. Is it the next Facebook? I believe this is partly Google’s fault: they released Wave to geeks and hackers and social media folks first. At Woobius, we’ve been working at resolving the problems with email for some time. What’s the problem with email, anyway? To most geeks, the main problem with email is spam. But then again, most geeks don’t do all that much document-based collaboration, by email or otherwise. In your average corporate environment, though, this happens all the time. So what are the problems with email in a corporate environment, and what does Wave do to address them? Problem 1: Collaborating on a piece of text Google Wave resolves that by effectively integrating Etherpad’s features into the email client. Conclusion
How to deal with :hover on touch screen devices
Are you planning a web project? Not sure what mobile strategy is right for you? Read our short educational article that can help you make the right choice. This article is a small case study about dealing with hover effects on touch screens. As you know, :hover behavior doesn’t exist on touch screen devices. While coding prowebdesign.ro we ran into double tap behavior twice: with pure CSS main menu drop-downs, and with portfolio sorting filter drop-downs (see Filter 1 and Filter 2 on this page). Problem was eliminated completely on all devices with screen width less or equal to 768 px. But what about touch screen devices with larger resolutions, like tablets? First of all, you need to decide what variant of layout you will want for those devices. To recap: at resolutions larger than 768px both main menu and portfolio filters on my site have drop-downs which are displayed on :hover. With filter drop-downs this sticky behavior was especially annoying. I’ve put together a starter template.