Zen Follower
- Join Date:
- Apr 2014
- Posts:
- 154
- Plugin Contributions:
- 0
Dover Fine Responsive Template
picaflor-azul:
Thank you for your input ;) Are you talking about the slimmenu? or the flyout menu (used from the fidelity template by sam wilson 3d)? As far as I know, both of these menus are switching the on hover to on click when the screen size reaches a certain width (slimmenu is 768px).
So, if I understand correctly, these tablet devices have a screen size larger than the 768 pixels and the on hovers are not changing to on clicks?
Thanks,
Anne
It was a mistake on my part as I didn't really look into the menu being used for this one. I see that the slimmenu is still being used but only the responsive toggle mode. And for the dover, it is using a flyout menu while the westminster/winchester is using the slimmenu full mode. So for the latter 2, both have hover as its main functionality. Rbauror is correct in that it does switch based on screen size which you have set the resizeWidth to 768px. So basically the issue of hover conflicts with tablet landscape in that the flyout and full mode slimmenu will show. And with hover needed to work, it won't respond to tablets in landscape.
So when I mentioned to modify it to use click instead of hover, I was speaking of when it was in the latter 2 views not the responsive toggle view.
But going back to user agents it is not the issue, I was only commenting on that as another user of the template kept referencing to user agents multiple times and wanted to address that. But to address the click/hover functionality, what I would do is to detect touch devices and then override the hover. Personally, that would be my sollution IF I used the template with the slimmenu built in. But since I had took away the code, I have not really dealt with it as it was out of sight out of mind.
However, I have completed a site using your westminster template and want to share 1 of the changes I did that I think would help functionality. This is for the easy responsive tabs. I had taken that code completely off as when it is in ACCORDION MODE, you may recognize that IF any of the accordion sections have content that is long like the description and reviews, any click on another section will move everything up and the visitor has to scroll up to view the start of the new section.
SOLUTION: Basically, I was browsing your older templates to see what was being used prior and I felt I found a very good compromise. I have used your accordion from your older version responsive templates. Bascially for those, it does not close the prior section so it does not force the user to scroll back up. So what I have done is to basically use TPP as the desktop/tablet view while the older accordion script for the phone view. You can add tablet to the accordion view as well, but for my friends purpose he opted to exclude it.
So bascially, it is a fairly simple coding which mobile detect does the calls. Just take the same logic from the calls in the header to pull the tpl_header files. Since my friend uses no switches this is the slimmed down version without sessions:
if ($detect->isMobile() && !$detect->isTablet() ) {
// phone device calls here
// such as echoing the div's for the accordion: layer, heading and content
// also used for calling the tpl_dgreview.php to force reviews when TPP not being used (NOTE: TPP does not need this as TPP calls the correct files from product_reviews both the header and template files accordingly.)
} else {
// tablet and desktop calls here
// such as calling the TPP code in 3 places
}
This is what I deem to be the best for functionality IF long accordion sections are used. Basically, over time a visitor who keeps opening up the accordions and has to scroll up to the start of the section may get frustrated and may interfere with sales.
