Re: configuring 10.63 like 10.10

Felix Miata <[email protected]> writes:

> 1-deselecting "show close button on each tab" (necessary to prevent
> accidental closings) causes the close button to disappear entirely
> instead of appearing over on the right side like I have configured in
> SeaMonkey and Firefox

It is possible that this is intentional, I don't know.  But file a bug
anyway.

> 2-file edit view go bookmarks etc are missing from space below
> titlebar and I can't find how to get them back

As someone else said, there's a "show menu bar" entry in the main menu
(and the File menu).

> 3-URL bar, menus, toolbars, dialogs, etc. are using tiny fonts instead
> of the same appropriate size designated in desktop font settings as
> such other apps like Konq, FF, SM, K3B, KPDF, etc use.

We have made some improvements in this area for Opera 11.  If it is
still wrong, file a bug.  There may be something we have missed.

Considering point 8 (using x11 dialogs), it is also possible that we're
looking at the wrong settings, since the settings in gtk/gnome and kde
are not exactly the same...

> 4-select font for menus, toolbars, dialogs etc require I select a
> family first in order to force size to an appropriate level

Interesting.  I suspect there is a technical reason for this, but file a
bug anyway.  We should be able to do better.

> 5- http://fm.no-ip.com/Auth/dpi-screen-window.html lies, telling me my
> 144 DPI desktop is 96 DPI on those rare occasions where it tells me
> anything at all, quite unlike Gecko (which always gets it right within
> rounding limits) and WebKit (which on every load always erroneously
> claims 96). If I reload enough times it will eventually tell me
> 96. http://fm.no-ip.com/Auth/Font/fonts-ptdemo.html does the same
> wrong things.

So, two bugs: No value displayed, and wrong value displayed.

For "no value displayed", the error console says:
Uncaught exception: TypeError: Cannot convert 'document.getElementById("pxsize")' to object

Which seems rather odd.  It could indicate that we run the onload
handler before creating the dom element for "pxsize" (but clearly, the
"inches" element is there...).  I'm no expert on the finer details of
this, but it seems rather odd to me.  A bug report would probably be in
order.

For the "wrong value displayed" issue, I'd have to investigate.  A bug
report is probably in order.


> 6-As yet I've found no way to lock the new tab button into any fixed
> location, like it always is in SM and used to be possible in FF. :-(

No idea.  I always remove it.

> 7-What if anything "Force DPI=144" in operaprefs.ini does I cannot
> tell. Once upon a time what it did was blatantly obvious.

The documentation says that it is used when choosing fonts (on X11).  I
suspect that documentation may be a little out of date...  It does seem
to be used to set some value, but what that value ends up being used for
(if anything) would take me some effort to figure out.

> 8-Open file requires I type in a fullpathname, offering no apparent
> chance to choose a local file to open from a list.

Fixed in 11.  You probably get the X11 dialogs for some reason.  In
Opera 11, the X11 dialogs should be quite usable.  Some may actually
prefer them over both the kde and gtk dialogs... (I think the valid
toolkit values are 0: automatic, 2: gtk, 3: kde, 4: x11.  1 used to be
Qt, but is no longer in use.)

eirik
--
Opera-Linux: https://list.opera.com/mailman/listinfo/opera-linux
More lists: https://list.opera.com/mailman/listinfo/
Unsubscribe: mailto:[email protected]?subject=unsubscribe