something like:
$("ul.jmolPopupMenu ul:not(:has(ul))").css({"maxHeight":"25em",
"overflowY":"auto"})
But I don't think that is quite it.
On Fri, Sep 16, 2016 at 1:16 PM, Angel Herráez wrote:
> I like CSS solutions; they are very clean and you do not mess up with the
> js
I like CSS solutions; they are very clean and you do not mess up with the js
code.
> something like "menus that do not contain any menus" --- li with no
> containing ul --- I think
that can be done in jQuery. Can it be done in CSS?
Not actually straightforward, since you cannot apply css to
something like "menus that do not contain any menus" --- li with no
containing ul --- I think that can be done in jQuery. Can it be done in
CSS?
On Fri, Sep 16, 2016 at 12:40 PM, Robert Hanson wrote:
> We might be able to implement that only for terminal menus. Have to think
We might be able to implement that only for terminal menus. Have to think
about how to do that.
On Fri, Sep 16, 2016 at 12:39 PM, Robert Hanson wrote:
> I registered 2700 MSIE uses in April; 1.4% of 189,000.
>
> On Fri, Sep 16, 2016 at 12:41 PM, Angel Herráez
I registered 2700 MSIE uses in April; 1.4% of 189,000.
On Fri, Sep 16, 2016 at 12:41 PM, Angel Herráez
wrote:
> > The way too long problem is generally solved by dragging the menu higher
> on the screen.
>
> I know. But still sometimes it's higher than the screen.
> In
> The way too long problem is generally solved by dragging the menu higher
on the screen.
I know. But still sometimes it's higher than the screen.
In many pages of mine the JSmol panel is 100% height, locked and cannot
be scrolled down (overflow:none), so it's actually impossible to reach the
That's right, because the menu is based on an array in Language.js, not
from a po file, like the word "Russian" is. Language is one of the classes
that is included in corejmol.z.js. (If it were any other way, it would
require loading all the language files initially.)
Anyway, that is fixed.
On
Fine, Bob
The funny thing was that the first string (language name translated to current
name) was correct, the second was wrong (language name in the original
language). If you siwtch to Russian, you can see in the same line one
correct, one wrong.
So I understand this is fixed for next
The way too long problem is generally solved by dragging the menu higher on
the screen. I'm not sure there is any other solution than that. It's a
standard jQuery menu. So if you can figure out how to solve this with that,
we could implement your solution in JSmol.
On Thu, Sep 15, 2016 at 3:29
Better -- I was missing the --charset UTF-8 flag on the Google Closure
Compiler command line.
On Fri, Sep 16, 2016 at 10:00 AM, Robert Hanson wrote:
> Hmm. This will be a good challenge.
>
> 1) The .java files are OK -- For example, Catal[`a] is correctly C3A0.
> 2) The .js
Hmm. This will be a good challenge.
1) The .java files are OK -- For example, Catal[`a] is correctly C3A0.
2) The .js files are fine.
3) In the developer console, everything is OK:
x = "Català"
"Català"
x
"Català"
4) The JavaScript is messed up:
x =
Dear Bob,
I have noticed two issues with the rendering of the pop-up menu in
JSmol-html5
1. The language submenu is way too long, and may become taller than the
screen, so in some page designs the lower half of the languages may be
unreachable.
2. The names of some languages display
12 matches
Mail list logo