Bootstrap 3 dropdown menu item in firefox - after click going to url - javascript

I'm working on 3 level navigation menu.
I find great example of menu on http://bootply.com/92442 which works pretty cool, but when I insert url addresses to the code the drop-down menu item don't open sub menu, but going to url. Here is example: http://bootply.com/109393
It only happens on firefox browser. On Chrome and Opera everything is ok.

Related

Safari Developer menu - show executed JS on event

Is there a way in the Safari Developer menu to show triggered/executed JS functions/code on events on a web page (for instance a button is clicked)?
Yes, it posible, first you have to enable the Inspect Element:
here a tutorial:
Choose Safari > Preferences, and click Advanced.
At the bottom of the pane, select the “Show Develop menu in menu bar” checkbox.
then open the Inspect Element and go to the 'Sources' tab
here you will see the Breakpoints and start play.

Navigation not working in IE8

I have a full width 3 level navigation, please see:
http://acemenu.zzcreative.com/test/logged-in.php
I am checking the menu across all browsers, in IE8 the menu does not appear when clicking the 'Menu' link.
Also I am told it does not work to well in FF on a PC?
Any ideas?
The menu displays in IE when you remove the z-index: 999 from the div with id sticky-header-logged-in

Dropdown navigation not working in IE10 browser but in rest its working fine

Example:
Dropdown menu is working fine in all browser but in IE10 submenus are not visible while hovering over main menu. very strange.
Below is the js used in this example :
http://www.steelecapital.com/pages/js/IBMenu.js
Dont know what was the issue but it strange.

Bootstrap's dropdowns close in less than a sec after pressing them (Android 4.2.1, stock browser)

There's a problem with Twitter Bootstrap's dropdown menus on mobile. If I use Android's stock browser and click on a menu, it will open and close in less than a sec without me doing anything else. The same thing happens if I press the dropdowns on the official Bootstrap site, so this has nothing to do with my code.
If you want to keep the dropdowns open and fix this, you have to tap them for a little bit longer, smth like 1 second. But obviously I'd like a simple tap to be enough.
Is this normal for Android's stock browser? In Firefox and Opera Mini dropdowns work just fine.
Thanks!
PS: no, I don't have any form inside dropdowns. Only links that work fine in other browsers.
This is an android browser thing. They handle links with dropdowns as both a hover and click. Other browser such as iOS handles menus with dropdowns as just the hover then another click to initiate the link.

How can Watir consistently deal with a javascript dropdown menu?

I am n00b to watir and I'm testing a web app that uses extjs. The app has a main menu with several items that have sub items. One of the main menu items has the same text as one of its submenus. In watir webdriver I have this code:
jobs_menu = d.p(:text => "Jobs")
jobs_menu.when_present.flash
jobs_menu.click
jobs_submenu_item = d.a(:text => "Jobs")
jobs_submenu_item.when_present.flash
jobs_submenu_item.click
This is supposed to flash and click the first menu and cause the submenu to drop. Then it should flash and click the submenu item. I get 3 results in 3 different browsers with this:
Firefox - 1st menu flashes and drops, submenu item flashes, but does not get clicked
Chrome - 1st menu flashes and drops, submenu item flashes and clicks OK - yay!
IE - 1st menu flashes and drops, then it goes away and the submenu item cannot be found with ElementNotVisibleError
Interesting to note for a different menu where the drop down text is different than the submenu text then Firefox and Chrome both work OK. IE still gives the ElementNotVisibleError.
How can I get this to work the same in all 3 browsers?
In some cases the display of menus does not require a click, and can be triggered by mousing over the menu. In that case it might work to try .hover instead of .click to get the menu to appear.
A problem with a lot of these custom controls is that they work differently on different browsers, which means your automation code MAY have to take that into account, this is the downside to custom controls like this and not using basic HTML elements

Categories

Resources