Westminster New

[DivaVocals]

Don't have time today to troubleshoot, but that change made no positive difference.

Galaxy Tab 3 800x1280 px
No initial detectable difference, Android/FireFox. menu still collapses
Android/Chrome replaces menu triangles (or arrows) with question marks. Collapsing menu still exists.

RixStix.. Go to the Slimmenu authors GitHub repo.. There's an issue I created where I tagged/linked/rounded up all the posted fixes for this known and annoying issue.. I tried them both and they BOTH worked for me on my Android devices.

[picaflor-azul]

Don't have time today to troubleshoot, but that change made no positive difference.

Galaxy Tab 3 800x1280 px
No initial detectable difference, Android/FireFox. menu still collapses
Android/Chrome replaces menu triangles (or arrows) with question marks. Collapsing menu still exists.

I have confirmation from several testers that it is working. Perhaps you have not implemented it properly on your site?

Thanks,

Anne

[RixStix]

I have confirmation from several testers that it is working. Perhaps you have not implemented it properly on your site?

Possibly. It could be cache/cookie/etc related. I'll try again later. All I did was copy/paste the code into the existing file.

Samsung GalaxyTab3 800 x 1280 px

[DivaVocals]

Possibly. It could be cache/cookie/etc related. I'll try again later. All I did was copy/paste the code into the existing file.

Samsung GalaxyTab3 800 x 1280 px

or it could be that there are characters in this code that don't belong:

html("▼")}

I saw this particular character throughout this code..

[picaflor-azul]

or it could be that there are characters in this code that don't belong:

html("▼")}

I saw this particular character throughout this code..

You are correct. Try the attached file instead.

Thanks,

Anne

[picaflor-azul]

Sorry, this is the correct attachment.

Thanks,

Anne

[RixStix]

Sorry, this is the correct attachment.

Maybe I should be a bit more specific. I have cleared history and cookies from both Android Chrome and Android FireFox browsers and see no difference in menu functionality before and after replacing the file. Maybe we are differing in our terminology.

Categories/subcategories have 2 tappable buttons each. The text and the arrow. Functionality differs depending upon which is tapped.
Tapping the text button, will cause sub-categories to appear but collapse.
Tapping the arrow associated with the categories will cause the sub-category to appear and not collapse.

My expectation was that either tappable button (text or arrow) should yield the same response/functionality and not experience collapsing menus.

Were your testers using an Android device with a screen resolution of 800 x 1280 px?
Am I looking for something different than this patch is intended?

Using Diva's github suggestion did not yield any different results.

[DivaVocals]

Maybe I should be a bit more specific. I have cleared history and cookies from both Android Chrome and Android FireFox browsers and see no difference in menu functionality before and after replacing the file. Maybe we are differing in our terminology.

Categories/subcategories have 2 tappable buttons each. The text and the arrow. Functionality differs depending upon which is tapped.
Tapping the text button, will cause sub-categories to appear but collapse.
Tapping the arrow associated with the categories will cause the sub-category to appear and not collapse.

My expectation was that either tappable button (text or arrow) should yield the same response/functionality and not experience collapsing menus.

Were your testers using an Android device with a screen resolution of 800 x 1280 px?
Am I looking for something different than this patch is intended?

Using Diva's github suggestion did not yield any different results.

I am testing with three Android devices and the behavior is corrected on all three..


I click the hamburger icon, menu displays, I scroll to the bottom of the menu and the menu does not collapse.
I click on the text of a top level menu item, and the menu collapses and takes me to the link associated with the top level menu item
I click on a submenu arrow and the sub menu appears. Again scrolling down does not cause the menu to collapse.
I click on the text of a sub-menu item, and the menu collapses and takes me to the link associated with the sub-menu item

Works perfect on all devices.. My test group Android and Apple users report that the functionality works as expected.

I did not expect that tapping the text and tapping the arrow icons would yield the same result.. neither did my test users (and I do not tell them what to expect because I want their GENUINE reactions)..

I expected that the arrows would open/close menus or sub-menus, I expected the text would take me to an associated link.. Perhaps this is because this is how a similar desktop menu would have behaved. So I don't expect DIFFERENT behavior on a mobile device.. I do expect that hover will likely not work on a mobile device..

[samisoaps]

While customizing the left slide out menu, I decided to change the name for the ezpages. Well, the ezpages weren't showing up after I did that! So I changed it back to Useful Links but they're still not showing up. I didn't change any ezpage or template settings in admin. Any idea? I've tried everything to get them back in the top drop down menu www.bellaornamenti.com Thank you, Andrea

[missesbeehaven]

Thanks for sharing this, I too have fixed this for my store that is using this awesome template :-)

Wanted to share this.. In the reviews sidebox, the text color is white on a white background.. This is a no no with the search engines.. Here's Google's policy:



I changed the following in the stylesheet to address

.sideBoxContentItem a, #reviewsContent a {
    font-weight: normal;
    clear: both;
    color: #FFF;
    margin-bottom: 20px;
    padding-bottom: 10px;
}
}

Note I simply removed the color:#fff;.. The links should now inherit the default links colors.