MySQL Bugs: #40781: Browser behaviour appears different on Safari when adding servers to group

Bug #40781	Browser behaviour appears different on Safari when adding servers to group
Submitted:	17 Nov 2008 12:27	Modified:	24 Feb 2009 7:20
Reporter:	Simon Mudd (OCA)	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S3 (Non-critical)
Version:	2.0.0.7088	OS:	Any
Assigned to:	Josh Sled	CPU Architecture:	Any

Description:
When adding a server to a server group a pop up appears with a list of servers which can be added.
The behaviour when clicking in the scroll bar between the selector and the end of the scroll bar is not consistent.

How to repeat:
When using firefox if you click on the right hand side of this list in the gap between the selector position and then end of the scroll bar, the page list seems to move forward a few entries at a time (though not a page as I would have expected).

When using Safari if you click on the right hand side of this list in the gap between the selector position and then end of the scroll bar, the page list seems to move forward a single server at a time (though not a page as I would have expected).

Suggested fix:
It would be better if the behaviour was consistent and I think also that the list of servers moved forward a page at a time.

Minor issue I know but reported so you are aware of it.

This is notabug with us, but maybe its one with Safari?  We don't control browser chrome, here.

It's sad that you come to that conclusion as it means that merlin does not work when direct access to the merlin servers is not possible. (hence the ssh tunnel).

We have another DBA in the US who accesses our systems and has the same issue.

This makes access to more than 1 merlin instance a real PITA, and as we're currently setting up a separate dev instance I've also bumped into this. When we continue with other production merlin instances which are planned this is only going to get worse.

Please put a big sign on your software:

This does not work with firefox if you try to access it through a common hostname....

I'm entirely upset by this, really.

Simon, I think you have this crossed with Bug#42390?  I'll follow up there.

Josh, you are right. I apologise.

I did not read through the ticket details properly, my comment was related to a different ticket and my reaction was inappropriate. I should have considered more carefully what I wrote.

As for this different behaviour I can live with that, although it does seem strange.