[css-d] Codeweavers CrossOver - Free download till midnight 10-31-12
Mac and Linux users, Codeweavers is offering a free CrossOver download till midnight tonight, 10-31-12. http://www.codeweavers.com/ CrossOver enables Mac and Linux to run Windows applications. Someone on my Linux list said it's been 4 years since they have done this. Matt __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Re : OT -- Crossweavers CodeOver - Free download till midnight 10-31-12
matt1027 wrote: Crossweavers is offering a free CodeOver download till midnight tonight, 10-31-12. CodeOver enables Mac and Linux to run Windows applications. And the relevance of this to CSS is what, exactly ? __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Re : OT -- Crossweavers CodeOver - Free download till midnight 10-31-12
At 14:24 + 10/31/12, Philip TAYLOR wrote: matt1027 wrote: Crossweavers is offering a free CodeOver download till midnight tonight, 10-31-12. CodeOver enables Mac and Linux to run Windows applications. And the relevance of this to CSS is what, exactly ? I agree that it's not directly related to CSS, but for anyone on the list who's wanted a Mac- or Linux-based Windows VM solution but hadn't gotten around to acquiring one yet, it's a good way to do cross-browser testing. So, let's let the thread end here in order to keep things on-topic; and if anyone on the list needed this, now they know what to do. -- Eric A. Meyer (http://meyerweb.com/eric/), List Chaperone CSS is much too interesting and elegant to be not taken seriously. -- Martina Kosloff (http://mako4css.com/) __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Codeweavers CrossOver - Free download till midnight 10-31-12
At 10:24 AM 10/31/2012, Philip TAYLOR wrote: And the relevance of this to CSS is what, exactly ? Good point, Philip! My apologies to the list. I had sent this announcement to a couple of other lists and hastily sent it to this one also, forgetting that this list maintains a strict focus on CSS. Matt __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] transform translate percentages and Android
Le 31 oct. 2012 à 19:43, Barney Carroll barney.carr...@gmail.com a écrit : [….] To demonstrate, here's a `transform`-based version of the same thing, which does the same thing as the previous fiddle, and works on all browsers that support translate3d… http://jsfiddle.net/barney/EJ7ve If you examine this on iPhone (again, by appending `/show`), you'll notice improved frame rate on iPhones. The same goes for Firefox running on Android, and arguably on Chrome and the default browser on Android too, except that here, the `translateX` offset of -100% somehow refers to the space occupied by all three tabs, so the wrapper slides just enough such that none of the tabs are visible. This is odd, since transform percentages are specified as relating to the full box model of the element being transformed — and computed style unambiguously describes the wrapper width as being the same as its parent (not, as the result implies, stretched 3-fold to accomodate the tabs). Can we describe this as a bug? If I understand correctly (no Android based device to test over here), Android default browser treats the inner width of .tabs as the total of your 3 ‘columns’ for the purpose of the translate3d transform ? And then only in portrait mode. Does G Chrome for Android work correctly ? That sounds yucky indeed. I don’t have any solution…. Does specifying .tabs { width: 100%; } help anything ? I also wonder if this has something todo with the way you write viewport meta (the correct way, using a column (,) as a separator). I seem to remember that had Android being buggy with that - they ‘accidentally’ allowed the use of a semi-column (;) instead, and have ‘better’ support for it (Mobile Safari drops everything after the 1st semi-column). PS - with Safari 6.01 on Mountain Lion, the text rendering after performing the translate3d transform looks quite poop - smoothing gone bad ? I’ve never seen that before. G Chrome isn’t great either, but not as bad as Safari. Philippe -- Philippe Wittenbergh http://l-c-n.com __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/