I list below all topic groups, which I have done according to subjects, which they handle. You can return to this topic group by using this menu and the link Table of topic groups on the top of the each page.
| ||||||||||||||||||||
![]() | Table of topic groups > Front page of CSS-guide > General info > Functionality of my pages with different browsers > Functionality of my pages with Opera browsers (section 2/4) |
|---|
The CSS-site like other sites or individual pages are rendered almost 100% as it is designed with Opera 6.01+ browsers both on screen presentation and printing (I give a list of reasons in the browser recommendation page).
Features, which I have used are such advanced features, which show that taking
account all media types and groups
the newest Opera has the widest CSS2 implementation. Of course Opera doesn't
support all, which is supported in some other new browser. As an example of
such features are some dynamic changes.
In general Opera renders Web-sites quite well. If sites are designed according to the widely used existing recommended specifications (like HTML 4.01 and CSS2) and they look out weird in Opera, the reason is in most cases in the authors. Web-sites are rendered in Opera incorrect commonly because of following reasons:
In these conditions Opera might render sites weird, links don't work or the
browser crashes (Opera however extremely seldom crash the whole operating
system; Reopening the browser it is possible to go to the situation before
the error happened and copy the problematic link to use it in another browser).
In my mind these errors are depending more bad designing than errors in the
browser (read
a cite
).
Opera is also a little bit sensitive to server problems. Because it tries
to render pages as fast as possible, it doesn't wait in bad connections so
much as MS IE, which might crash Opera.
I use have used Opera because of the following reasons:
(I use commonly a CSS-file, which you can download
to yourself
).I admit however that also MS IE has handy features (it is possible to install into MS IE a powerful search engine).
).
The sibling window doesn't remain on the background if windows are tiled.
Opera use its own window system. It doesn't download the whole interface
of the browser but just a new window with one toolbar (the user of MS IE
or Netscape must get the open windows from the task bar of Windows (or with
ALT + TAB keys), which is troublesome).
From the 6.x series it is possible to use the single window interface, when
opening a new window opens a new interface.
.Opera browser don't have many such missing features, which limit Web-designing, but I found following two features, which have caused for me limitations:
).
This is not a big problem because it is possible to create DHTML/
DOM-menus
,
which appropriate designed work also in Opera. Opera 4.x-6.x has the limitation
that dynamic menus must base on changing values of the
visibility property because dynamic changes of the display
property don't work.overflow:auto. The consequence is that,
only the IFRAME element can be used to create navigation systems,
which need scrolling.cursor
property, which could get in certain circumstances better presentation or
better information than with the build-in cursors.Browsers have also following minor CSS-problems:
must define with a certain way in order to get them work optimal.
rendering note How to set CSS for table elements (an
example
)
Opera puts to most the narrows cells, which are on the right bottom borders
even if it should not do so. This matter is fixed in the Opera 7.x series.IFRAME, OBJECT
below the fixed positioned elements (the stacking order doesn't work in
any browser with embedded plug-ins applications completely correct). Concerning
older versions than Opera 7.x this concerns also some form control elements
(for example INPUT).In addition I have found following are other functionality problems (Opera 5.12 has the most less generic functionality problems):
| Sections of page: | First section | Previous section | Next section![]() | Last section![]() |