KingMotley (944240) writes "Although generally overshadowed by the iPad 3 debut, Apple also introduced the third incarnation of its Apple TV streaming media players this week. The third-generation Apple TV adds full 1080 support, a much faster processor, and much to its predecessor, and a completely revamped icon based UI. The revamped UI and faster processor (the same as from the iPhone 4) is leading some to believe that the device may be headed down a path where it may get its own place in Apple's App store eventually, embracing 3rd party apps. Considering how little effort Apple has put forth for the product, even Apple must have been take by surprise when all available stock for the revamped device sold out in under 8 hours." Link to Original Source top
KingMotley (944240) writes ""Most PC users hit the web using Internet Explorer by default, simply because it just works. Now, after antitrust investigations, European users were given a choice of browser to install via ballot screen, and initial reports are great for 'ol IE. According to Statcounter, IE use in the UK has gone up 3.39 percent since last month's implementation of the ballot, 1.54 percent in Italy, and 1.76 percent in Germany. It's still early days, and it'll take more than this for IE to reclaim it's 95 percent lead in the browser war, but it's certainly a good trend for Microsoft. With that in mind, we're going to have to ask you to place your bets now. As a side note, all other major browsers (Firefox, Chrome, and Opera) have seen a dip in their usage for the same period."" Link to Original Source
While writing HTML5, the W3C group seems to have broken compatibility with HTML 4 again. No longer can you specify colspan='0' on a td tag to let it span the rest of the row. (sigh) I guess it wasn't all that important since only firefox ever implemented it correctly in the first place. Opera did support rowspan='0' as well, but that is no longer valid in HTML 5 either.
Firefox misinterprets the CSS3's Editors draft and ignores any CSS properties (like transition) where an angle or time specification is given as simply 0. All other browsers accept 0 for the time specification, and the CSS 3 specification says that it is to be backwards compatible with the CSS 2.1 specification that clearly states that the unit of measure is optional when the unit is 0. Bad mozilla, bad!
Supposedly there is a fix coming, but not in time for our latest release. Yay for having to delete all our pre-min'ed files, and recreating them without the debug comment that is typically there to help debug in chrome. Oh well, at least there is a workaround.
Apparently Chrome has a bug when dealing with padding on elements with display:table. They've had one for a while, and it APPEARS they hacked it to always assume subtract the padding from the element's width, which is fine except for when you are in box-sizing:border, they still subtract it. Fail. Chrome breaking standards based layouts. Yes, it's been reported, "fixed" but broken in new and interesting ways -- for over a year.
As part of doing due diligence in creating websites that are accessible to the handicap, being able to use semantic markup is paramount. For forms, this means grouping logical sets of form elements, and wrapping them in a fieldset tag. As part of one of my most recent web designs, we used the fieldset to encapsulate groups of common tags that were collapsible. Well, that was until we found out that we had to bastardize our markup because firefox's implementation of the fieldset tag doesn't allow you to have content that is larger than the visible area that is. Yup, firefoxes implementation acts like it has overflow:visible stuck on, no matter what overflow setting you give it. Boo firefox for forcing us to wrap our pretty fieldsets in divs just because of your broken implementation.