As far as I can tell from the documentation, the semicolon is required as part of the syntax for entity reference. So a non-breaking space must be not  . However, it looks like Safari is the only browser that DOESN'T render entities without a semicolon. Does anyone know why? Both Safari and Chrome use webkit, yet Chrome renders regardless of the semicolon.
It's the input part of the principle of Generous on Input, strict on output. Different browsers choose different measures of "generous".
Related
The problem: Old dinosaur working with outdated html/css styling. This dude managed to enter a whole bunch of input field sizes using
Style='width:80' and similar. That's right, without any 'px' or anything.
Now this works satisfactorily in MSIE 10 and above as well as Chrome and Firefox, but unfortunately the interface also has to support MSIE 9 (I have not even dared to attempt MSIE 8....) and MSIE 9 really does not like this. Fields just seem to have some random/default length and everything looks horrendous.
Replacing all the instances of this is a task more daunting than coming back from the dead (a general replace will only be moderately useful) so the question is...
Is it possible to set "THE" unit in CSS so that it is applied to all fields that are missing one? Use of jQuery is OK, it is already jQueried up the wazoo so that's fine. But please tell me this is at all an available option... or I shall find myself going mad replacing 1000+ fields...
No, it is not possible. Units must always be defined, except for value 0.
But it shouldn't be that daunting, surely a regexp or two will handle it?
does file search and replace with sublime text like Style="width:(.*?)" with Style="width:$1px" work for you?
Specifically in Firefox. We look at code in the browser often, and I am wondering if we could configure the browser so that tab characters show up as 4 spaces wide, instead of the default 8 spaces.
Edit: no responses yet. So I assume this is not possible?
Not really the answer you are looking for but maybe you could replace the tab characters with the appropriate amount of spaces and use the "pre" tag?
It is definitely worth looking at the html source to see how sites like stackoverflow.com deal with displaying source code.
I'm looking for an easy way to show a JSON-like response from our server in Opera. It should be easy to read, e.g. in a tree-like fashion.
If I use Dragonfly I only get to see the response wrapped in an HTML-body element.
Is there a plug-in out there? What do you use for this? I'm using Opera 11.50.
I know I could use Firefox and its plug-ins, but it would be much more useful in Opera.
Did you check addons.opera.com? There is one called JSONViewer.
Check "Source" extension for Opera, it shows and highlights a lot of formats (incl. JSON).
Is there a cross-browser compatible way to post a form in one tab of the browser to another (which I know is open and is of the same domain)?
I tried window.name='some_name'; and target='some_name' on the form, but this does not seem to work. Am I missing something?
There is no standard to how tabs are handled via javascript, so you are out of luck.
Most browsers these day also make sure each tab is segregated/partitioned from others, as much as possible, so this is unlikely to change in the recent future.
The closest you can get to posting to a different page is to use AJAX, or possibly using frames.
Is there any CSS filter can be applied to detect IE6's standard mode and quirk mode?
The story is that a jQuery script is using $.support.boxModel to handle different rendering mode. But the CSS use the *width hack to define the dimension. But this hack can only filter whether the browser is IE but not the real rendering mode IE is on.
You can't do it in css, but you can include different stylesheets for different versions of IE using conditional comments.
Why would you need that? Usually you write a style sheet for one explicit HTML document or at least one specific site where you know whether that page/site is running in quirks or standards mode.
It's not like a page can unexpectedly change modes :-)
If you really need to support a mixture of pages with different modes you'll need to use two separate style sheets, one for each mode.
I ended up using js injection
if(!$.support.boxModel) $('body').addClass('nobox');
And then do the styling in CSS.