4 ms·
My favorite part is the WebKit specific code... Don't be Evil and something about standards right? This is like IE4/Netscape Communicator days all over again,
by BigChiefSmokem 13y ago
My favorite part is the WebKit specific code... Don't be Evil and something about standards right?
This is like IE4/Netscape Communicator days all over again, except now with more than two dominant browsers...
"I was a web dev in the 90s and all I got was this lousy XMLHttpRequest object"
- abraham 13y ago> My favorite part is the WebKit specific code... Don't be Evil and something about standards right? Meaning what? Google isn't directly involved with WebKit anymore and can't make them implement standards.
- BigChiefSmokem 13y agoGoogle and Apple are the reason we are back to this mess again. They need to fix the problem not facilitate it with tools like this. Microsoft and FrontPage did the exact same thing back in the days.
- andybak 13y agoAre you saying: 1. This tool can't produce cross-browser output 2. This tool includes some rendering engine-specific markup to solve cross-platform issues. 1 is unlikely and 2 is benign.
- niveshr 13y agoHi, While editing a file, Google Web Designer uses -webkit prefixes. However, when you publish your content, the publish dialog allows you to specify additional vendor prefixes (or no prefixes) in the output so the content works in different browsers. I hope this helps. Thanks, Nivesh (Google Web Developer)
- polskibus 13y agoCan you explain the reasons behind this behavior?
- gwdengineer 13y agoHi, Google Web Designer (GWD) uses the WebKit HTML rendering engine inside the application's workspace and reports the styles that are actually applied to the content during editing. Thanks, Google Web Designer team
- eranation 13y agoThought so too, but when you publish they let you add FireFox / IE CSS prefixes (on by default)