Tibia makes heavy use of popups for document editing. If you are
running a popup blocker, you should check the following two items:
- Whitelist. You should register your own domain in the popup-blocker's "whitelist", or list of allowed domains.
- Popup limits. Some popup blockers limit the number of popups
even if your domain is whitelisted. In Firefox, for example, you should
change the about:config value of dom.popup_maximum to a large number.
Firefox is a fast, secure, open-source browser created by the Mozilla Foundation. Download it.
Firefox 1.0 is fully compatible with Tibia. There are no known issues, provided you turn off caching of webpages. Tested builds:
- Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Mozilla has other, older browser releases besides Firefox.
No known issues. Tested builds:
- Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910
Internet Explorer is made by Microsoft. If you don't already have it, it's not worth getting.
IE6 has a few problems with Tibia; you might find them annoying enough to switch to Firefox.
- Element highlighting. When you load a document from the
server (in order to edit it), Tibia tries to highlight each element
(which you have permission to edit)
by drawing a border around it. Internet Explorer doesn't provide a way
to highlight only permitted elements; therefore, all elements will be
bordered whether you are allowed to edit them or not. This means you
will have to use trial and error to discover which elements you can
edit. If you're using Tibia on your own
personal website, this probably doesn't matter, because you're probably
an admin, and admins can edit everything.
- The whole document. Documents which you load from the server
should have a DOCTYPE declaration. IE doesn't provide a means for us to
access that information; therefore, when you save your document, this
information will be lost. This is particularly important when using
Internet Explorer, because the DOCTYPE can drastically change how a
page is displayed in the browser.
- Hyperlinks and buttons. Hyperlinks are links to other
documents or websites. For the most part, these will be disabled while
you edit a document. However, elements can also
have an 'onclick' event. When you use Internet Explorer, Tibia cannot
disable these (at least not without changing your document, which would
be magical and a bad idea, but might happen in the next version of
Tibia anyway ;). So be careful what you
- Image file locations. When you double-click an element, Tibia
loads its content into the edit window. Images don't have "content" in
that sense; therefore, Tibia loads the filename of the image, so you can
replace one image with another. Now, some images have a relative
pathname (like "logo.gif"). The concrete location of the image is
relative to the document you are editing. Internet Explorer,
supply us with this relative path; instead, it resolves the path to a
concrete one, so that "logo.gif" is changed to
"http://www.mywebsite.com/app/branch/logo.gif", for example.
- Plain text files. When a browser displays a plain text file
(Content-type: text/plain, text/css, etc) it still wraps that text into
an HTML element and usually a body and pre element. IE, however, won't
tell us the Content-type of the document, so we can't reliably strip
out this HTML cruft. But that's OK; many text files (like .css, and
.js, that Firefox shows in the browser) get punted out to Notepad by IE
- Microsoft Internet Explorer 6.0.2800.1106IC (128-bit) on Win2k
Not tested. Anyone?
- Apache/1.3.3 on Debian GNU/Linux (kernel 2.2, sarge/sid), CGI only
- Apache/2.0.47 on Win2k, with mod_python 3.1.3.win32-py2.3 and without
- Microsoft Internet Information Server (IIS) 5.0 on Win2k
- Python 2.3.2 on win32 + PIL 1.1.4
- Python 2.3.4 on Debian GNU/Linux (kernel 2.2, sarge/sid) + PIL 1.1.4 (python-imaging)