Skip to content
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

Select Tag unclickable on Mobile #320

Open
Mendez83 opened this issue Jun 25, 2019 · 3 comments
Open

Select Tag unclickable on Mobile #320

Mendez83 opened this issue Jun 25, 2019 · 3 comments

Comments

@Mendez83
Copy link

Mendez83 commented Jun 25, 2019

Hello,
I am doing some test and I have problem when the item i make sortable contain a select tag that become unclickable on mobile.

Any workaround for this?

<ul id="e_list_catalog" class="connected_list_e list_container">
    <li class="list_item_e_id" id="1">
        E01
        <select>
            <option value="0">30"</option>
            <option value="1">1'</option>
            <option value="2">2'</option>
        </select>
    </li>

    <li class="list_item_e_id" id="2">
        E02
        <select>
            <option value="0">30"</option>
            <option value="1">1'</option>
            <option value="2">2'</option>
        </select>
    </li>
    <li class="list_item_e_id" id="3">
        E03
        <select>
            <option value="0">30"</option>
            <option value="1">1'</option>
            <option value="2">2'</option>
        </select>
    </li>
</ul>
@RWAP
Copy link

RWAP commented Jul 6, 2019

Try my own fork of this project - it has various fixes one of which helps with sorting:

https://github.com/RWAP/jquery-ui-touch-punch

@jonfen
Copy link

jonfen commented May 7, 2020

I have the same issue.

@RWAP
Copy link

RWAP commented May 7, 2020

The problem is more to do with the grab area - when you put your finger on the select, there is no way of knowing if you are trying to drag it or click onto the select link.

Have you tried the updated fork of this project - if so, raise the issue on that fork, not on this ancient version of code which has not been updated for some years

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants