I am using the latest version of TinyMCE which will render in IE9 but I cannot interact with it.
Removing document.domain will allow it work again, but I need document.domain to make the popup windows in tinyMCE work in my setup.
I have tried using <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /> and such but this doesn't seem to make any difference.
Related
I have created a fully responsive website based off of the Bootstrap framework.
In the browser all the responsive features are working exactly as I want them to, however, it doesn't seem to be working on my iPhone. I'm still seeing a full size site.
Has anyone had this issue or would know what might be the cause?
You almost certainly forgot the <meta name="viewport"> tag the Bootstrap docs mention. In your <head>:
<meta name="viewport" content="width=device-width, initial-scale=1.0">
edit: Now that you've provided the URL, check out the syntax highlighting on this line:
<meta name="viewport' content="width-device-width, initial-scale=1.0"/>
You've opened with a double quote and closed with a single quote.
So I have a GWT application that works perfectly in IE6-8, and most all modern browsers. Unfortunately, due to a known bug in how IE9 handles onchange events on <select> elements, it's pretty much unusable in IE9.
So instead of having our clients downgrade to IE8, I had the brilliant idea of having IE9 emulate IE8. I put this meta tag in my GWT host page:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" >
When I look at the IE9 Developer Tools (F12), I see that it's "Browser mode" is IE9 and "Document mode" is IE8 standards. The GWT app doesn't load, though: it gives me a JavaScript error in one of the compressed and obfuscated JavaScript functions generated by GWT. I don't have the ability to debug into the app via IE so I can't figure out what's going on that way.
I suspect it has something to do with the way GWT detects which browser is being used and loads the appropriate resources for the session.
Edited to add: When I try to use IE=8 instead of IE=EmulateIE8, Developer Tools still reports a IE9/IE9 standards mode and all of the same onchange event issues are present as when I run in vanilla IE9.
Is there a working way to make IE9 emulate IE8 Standards mode in the way the http-equiv meta tag does, that works with GWT 2.4?
I've had similar problem: IE ignored <meta http-equiv="X-UA-Compatible" content="IE=9"> tag (I was trying to prevent IE8 from displaying the page in IE7 compat mode). It was caused by not having X-UA-Compatible meta as the first child of <head>. I set it as the first child of <head> and added <!DOCTYPE HTML> on top of everything, and it worked.
I am a new user to fancybox 2.0 and have to been able to get it to work. After a couple of days trying, I eventually stripped down test page do the bare bones. It works with Firefox but not with IE8.
Please, can someone look at this code and see where I am going wrong.
http://www.bytebrothers.com/bb_tester/Video_lightbox_test.htm
Your document has not DOCTYPE so IE switches to quirks mode.
Fancybox needs standards mode to run properly so set a valid DOCTYPE. You can check http://www.alistapart.com/articles/doctype/ or simply set <!DOCTYPE html>
I am trying to figure out if there is a way to use LESS or SCSS without having to save the document or refresh the browser. At the moment I use CSS Edit which is great for live previews but I cant find a way to get the live previewing to work with LESS or SCSS. My ideal situation would be to get a truely live (or as close to) setup working with Textmate and my broswer. I have looked at a few options, WebPutty is great but it's in Beta and web based so I'd love a solution that could fit into my existing workflow.
Many thanks
This might be what you're looking for: livereload.com
I only just found this myself while Googling for the same problem, Haa!
It's currently only for 64-bit Macs. Its also in beta..
Windows version under dev.
Can't seem to find a link to the v1 that is mentioned on the site?
If you're using static files you can use this code taken from http://f.cl.ly/items/0y2G351r3O3T3j1b401u/Live-LESS-previewing-in-Espresso.html
<!-- Link directly to LESS stylesheet first -->
<link rel="stylesheet/less" href="style.less" type="text/css" media="screen" />
<!-- Then link to LESS, and enable development watch mode -->
<script src="less-1.2.1.min.js" type="text/javascript"></script>
<script type="text/javascript" charset="utf-8">
less.env = "development";
less.watch();
</script>
<!-- Voilà! Instant LESS previews in Espresso -->
However, if you are using localhost, I've not figured out how to get this to work yet.
Check out EDGE. http://getedge.io - it let's you live edit Sass and LESS files from Sublime Text or Textmate. No need to save the file - it updates as you type. You can sign up for the private beta right now.
There is no complete solution for what you are looking.
Chrome dev tools (with sass source maps enabled) is your best bet but I don't think you can do mixins
http://livestyle.emmet.io/ is another option you might want to try
Brackets works well with live changes but applies only for chrome
Here's what I do and it serves the purpose and works like a charm in mac/pc and linux
Have one terminal open that does sass --watch
Have another terminal/app that lets you run live-reload
Your sass will compile and as soon as your stylesheet changes all your browsers get refreshed
But you can't do style injection with this, meaning the page WILL refresh (if you want to theme dialogs, you will have to open them again) But there are other tools available for style injection as well
Hope this helps!
live.js is your solution :)
It doesn't not only work with html, js, css but also less.
You have to trick it with filetype of css:
<link rel="stylesheet/less" type="text/css" href="stylesheets/main.less.css">
Tried the bookmark version on rails local server. Works a breeze!
CssRefresh
My co-worker and I whipped up http://less2css.org the other day. Allows you to choose the version and see your less converted in realtime.
Hope it helps someone.
I think there is no such add-on right now, but I'm also a fan of Live CSS Editor (if that's what you meant by CSS Edit).
I think it would be useful to have something similar with SASS or LESS support, so I made a quick prototype for such Chrome add-on (analogue to Live CSS Editor). It includes syntax highlighting and LESS support with use of client-side LESS library. It's not user-friendly yet so not a candidate to the Chrome Store, but here is it's Google Code Project where it can be downloaded and loaded into Chrome as unpacked extension. I'll try to improve it over time, but anyone else can try too ;)
Screenshots and a bit more are in this blog post.
I'm creating an application using GWT 2.0.1; it complies 6 computations and runs well in all browsers except IE8, it shows a blank page( but can be viewed in IE8 compatibility mode) .
When I add the line in my gwt.xml
<set-property name="user.agent" value="ie8" / >
it compiles just 1 permutation and the application displays fine in IE8. However if I add the line
<set-property name="user.agent" value="ie8,gecko,gecko1_8,safari,opera" />
it compiles all permutations, but the application still cannot be viewed in IE8 but runs properly in all other browsers.
Is there any other method to ensure my application will run in all browsers ?
According to this page besides setting the proper user agent you have to add the following meta tag to enforce IE8 standards mode:
<meta http-equiv="X-UA-Compatible" content="IE=8"/>
For those who are looking for a nice solution, you have to insert this line :
<meta http-equiv="X-UA-Compatible" content="IE=5,6,8,9" >
in your .html file (the host page)
This will ensure that your page is compatible with ascendant IEs...
I had a similar issue once and the problem was that the HTML page that bootstrapped the GWT JavaScript had an unmatched HTML tag. This didn't cause a problem in Firefox or Chrome, but IE just displayed a blank page. Try verifying your HTML using an HTML Validator. The W3C validator is a the cannonical service.
http://validator.w3.org/
instead of
<set-property name="user.agent" value="ie8,gecko,gecko1_8,safari,opera" / >
Try diffing the generated permutations for IE8 when you use <set-property name="user.agent" value="ie8" / > and when you use <set-property name="user.agent" value="ie8,gecko,gecko1_8,safari,opera" />. If they are different, you might get some clue to take forward your investigation. Use fiddler or IE developer tools to monitor and compare the names of *.cache.js files being loaded in each case.