-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vendor contact form improvement suggestion #221
Comments
@davidsherlock full custom or are you using a library to implement a tabbed interface? Requires a page load or switches tabs in place? |
Was just a small bit of JavaScript, HTML and css mainly, no custom libraries or alike. It's possible a better way of doing it exist but I wanted a quick solution! Just feel it's a better layout for the profile page so the contact form isn't easily missed.
…Sent from my iPhone
On 26 May 2017, at 20:58, Sean Davis ***@***.***> wrote:
@davidsherlock full custom or are you using a library to implement a tabbed interface? Requires a page load or switches tabs in place?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I agree totally. I experimented with a few other layouts but ultimately chose to put it at the bottom. I might revisit again eventually. It's not high priority at the moment. |
If tabs are implemented you should make sure they can be linked to directly and the relevant content is shown. |
@spencerfinnell no doubt about it. Learned that lesson on EDD site's account page. |
I agree a modal box is a bad idea, however I have a better suggestion for the vendor contact form to position it better within the vendor page so it's not just dumped at the bottom of the page.
My idea was to use tabs, which would allow for the contact form to be hidden initially until clicked. Here is a screenshot of my rough implementation (still reworking the look of it).
The tabbed approach would have a few advantages such as allowing additional tabs for a larger about page, vendor public wishlists/collections, etc. Just an idea that might be worth considering!
The text was updated successfully, but these errors were encountered: