Live view css3

Question

Hi you guys. I am looking for some input.  I am playing around with some of the new properties in CSS3. There is some really great stuff out there now that you can do with CSS3. One of the properties I am playing with is
-moz-transform:rotate(30deg); (NOTE IT IS FOR FIREFOZ ONLY)
If you assign  it to an ap div, it turns that div at a 30 degree angle. Pretty cool.
But what I am finding out is, when I hit the live view button, the Live view browser does not appear to be the Firefox browser and that property is particular to firefox In other words when I click live view, I can not see the box turned at a 30 degree angle. I have to actual hit F12, to see it in my primary default browser, Firefox. I don't want to have to hit f12. I want to be able just click the live view and see  the page as it would be seen in a FireFox browsers. Is there anyway I can change the browser live view renders in?
Please let me know. Thanks for all your help.
-moz-transform:rotate(30deg); /* Firefox */
#apDiv3 {
position:absolute;
width:200px;
height:115px;
z-index:4;
left: 394px;
top: 78px;
background-color: #99CCCC;
-moz-transform:rotate(30deg);

Answer 1

www.aimeecaprice.com wrote:
Hello, Thank you for your quick reply.
I did try changing the property to a webkit property and live view did display it then, however I want live view to display the Mozilla Firefox property.
There must be some way to change that live view browser  from webkit to firefox, don't you think? Let me ask you this, how did you find out that dreamweaver live view uses web kit. Was it in the help manual? or did you just figure it out by process of elimination?
Adobe has openly said in blogs and in the release notes that the Live View uses the Webkit engine.  This was primarily targeted because of how they were perceived as being slow and hanging onto Flash.  Webkit is the engine that powers Safari and Chrome on the desktop as well as iOS and Android on the mobile front.  Unfortunately, because of how Webkit is tied into DW there is no way to "swap out engines".  Believe me when I say, Mac users would have loved to have been able to "swap in" the IE rendering engine and Windows users could say that as well with the IE6, IE7, IE8, IE9 and IE10 engines (the last 2 are the least problematic).
If you are truly developing for CSS3 and cross-browsers, using the -webkit and -moz prefixes in addition to standard CSS3 is recommended since IE falls under neither prefix, and the same should go for Opera as well.  While it may seem bothersome, I can assure you it is no where near as bothersome as HTML5 video where the big players (Apple and MS) currently support the proven MPEG-4 video technology whereas Firefox currently supports Ogg and Chrome wants to move from MPEG-4 to its own propriety format WebM.  So not only in this case do you need extra code in your pages but you need to re-encode your video multiple times.
So the short answer is that it's best not to develop for just one browser.  It will be a bad habit that will be hard to break.