Browser requirements
Tag cloud: (all tags)
2018
2019
2021
2022
2023
about.com
account
acronym
address
addthis
admin
admin_forum
administration
adsense
alexa
alive
analytics
anchhor
anchor
animoto
anobii
anonym
anthropology
api
app
apple
application
appplication
architecture
area
art
ascending
attached-files
attack
attributes
australia
autocomplete
automatic
autonumber
autonumbering
autosave
backgound
backlinks
backup
backup-stuck
backwards
badge
band
banner
batch
Time in Toruń, Poland
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-Share Alike 2.5 License.
I have noted that different browsers may read wiki sites differently. For example, an image shows perfectly well with Mozilla Firefox, but not with Windows explorer.
Is there any explanation or solution to this?
Many thanks
Lets communicate
Explanations are many available - the different Developing Policies of the browser-companies… their own different releases… ( I use Interbet Explorer 8 here ( not 9 !) IE 7 on my Laptop ( whicjh is really poor), and FF 5 here and FF 3 on my laptop.
"CCS3" - the newest "standard" in Cascading Style Sheets is not yet integrated in IE 8 - as an example… and not fully in most others..
Solutions ?
You can only test your laout on all free available browser for your own ( IE, FF, Chrome , Safari in all their different releases)
and ask our Guru's here what you can do to make it as equal as possible in all browsers..
Have you an example of a specific page for us?
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
Further to Helmuti's answer, the problem has always been the speed at which different browser organisations implement new CSS features. And occasionally the logic behind some things differs between vendors. Google Chrome has always been pretty quick to implement new CSS and Safari and Firefox (which is what I use as my default) are also also up there. Microsoft has also been slow to release new versions of Internet Explorer, possibly due to the complexities of bundling IE with Windows. The problem this has meant for developers is that browser specific rules have had to be used. So, for example, for a long time we had to use rules like -moz-border-radius (for Firefox) and -webkit-border-radius (for Safari), but these were vendor-specific, so any browsers that didn't have their own equivalent and couldn't read them, like IE8 and below, ignored them. However in that particular example we can now use border-radius which is read by all the major browsers including IE9.
It is possible to target specific browsers in your css. So if an image border looks Ok on most browsers but not on IE7 or IE8 for example you could set a specific rule which would only be read by those browsers, for example:
But in general it is not good practice to use these "hacks" (which always seemed to be needed on IE!) as it makes the CSS more complex and harder to maintain. Best to try to find another way around the problem.
The problem is getting better and has improved considerably since the release of IE9, and IE10 is in preview. Although as Helmuti has pointed out, not everything in the CSS3 spec is fully implemented in all browsers yet. But rendering of sites is getting more consistent across current versions of browsers, and the roll-out time for new releases is reducing which also helps. But I think many of us still try to test our sites on Chrome, Firefox, Safari, Opera and several versions of IE to make sure there are no major issues.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.