I've tried Tiny MCE from 2014-10-30, but in IE8 all icons are shown vertically instead of horizontal. Here is a example:
In IE9 it worked out of the box. But for IE8 I had to add this code in the head of my HTML-document:
<meta http-equiv="X-UA-Compatible" content="IE=edge">
Related
Edge defaults to IE8 when displaying our app.
Tools->Compatitibity View Settings
the list is empty
the "Display intranet sites in Compatibility View" is NOT checked
The website is actually treated as "Internet"
We have tried both with and without
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
In short, try as I might Edge defaults to IE8.
I've got a site running aimed at touchscreens running Firefox (very specific I know, but it will hopefully help with a solution)
On the page in question, I've got a d3 map that I'm trying to enable pinch zooming for, however any pinch gesture is causing Firefox to set the zoom for the whole page. Is there a way to prevent the page zooming and only allow the map to zoom?
It's not an issue if I have to modify Firefox config settings but I'd prefer to avoid it and rely entirely on javascript if possible.
Thank you in advance
You might be able to do this using the viewport metatag and Hammer.js
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" />
This will disable the default browser zoom.
You can then use Hammer.js to capture gesture events which you will then pass to your D3.js code to zoom your map
I'm having trouble with a full-screen (saved to home screen) iPhone web app on iOS7.
Typically, when an input is selected, it has scrolled into view above the keyboard.
However, this doesn't seem to happen on iOS7 for scrolling DIVs in a full-screen web app.
Thus, when a DIV uses "-webkit-overflow-scrolling: touch" and an input in the bottom half of the screen is clicked, the keyboard is fired, but the input doesn't scroll up.
AND, at that time, the input won't respond to any further onFocus events that I could otherwise scroll it up with.
Anyone seen a workaround?
Updating the viewport meta tag fixed it for me.
I changed this:
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, user-scalable=no" />
To this:
<meta name="viewport" content="width=device-width, height=device-height, initial-scale=1.0, maximum-scale=1.0, target-densityDpi=device-dpi" />
height=device-height is the actual fix (without it the viewport gets resized to accommodate the keyboard).
It worked on my WebApp by removing the height settings.
I'm helping build a site for a client in Adobe CQ5. Due to the preferences of the client I cannot post the source, but we are having trouble with IE8.
When we try to view the site in IE8 the page will not render. When using the dev tools we can browse the HTML and the select tool does successfully highlight elements with the blue outline, but none of them render. The page is simply white. Things render properly in IE7 browser mode but not in IE8 or IE8 Compatibility Mode.
I've run the html through the W3 validator and nothing egregious jumped out. Anyone have any leads?
there must be some javascript error which causing this. otherwise CQ5 render well in ie8
If it works in IE7 but not IE8 you can try adding this to the <head> section
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
This forces IE7 emulation. You can also try playing with the doctype to see if this makes any difference.
What are the pros and cons of adding
<meta http-equiv="x-ua-compatible" content="IE=8">
to a website. I would like IE 8 to render in the IE 8 Doc mode so styles are more cohesive across browsers. I am just worried about negative consequences of adding this.
IE8 will render in IE8 standards mode if you provide an appropriate DOCTYPE, like <!DOCTYPE html>. <meta http-equiv="x-ua-compatible" content="IE=8"> is unneeded to force it in this case.
The only consequence of adding it though would be that the soon to be released IE9 will render the page in IE8 compatibility mode. But if you really really wanted to add it for some reason, and still keep IE9 in its own standards mode you can work around it with a conditional comment
<!--[if IE 8]>
<meta http-equiv="x-ua-compatible" content="IE=8">
<![endif]-->
I just really don't see a point to adding it though. Just have <!DOCTYPE html> that will ensure standards mode in ALL browsers (including even IE6).