I need to disable the ion-range while scrolling the page ,im going to detect the ion content scroll with
(ionScroll)="onScroll($event)"
than i would call a function to disable the ion-range, is there an attribute for disabling it? i didnt find it in the documentation. Thanks!
You could try to use an input with type="range" and the ng-disable directive. Something like this:
<input type="range" name="[name]" ng-disabled="[your-condition]">
Maybe this post in ionic forum could help more.
https://forum.ionicframework.com/t/disable-range-selection-with-toggle/26027
Hope it helps!
Related
I have my simple application using Ionic Framework.
It looks like :
Here the list code :
<ion-list show-Reorder="data.showReorder">
<ion-item class="item-avatar item-icon-right" ng-repeat="band in bands" type="item-text-wrap" href="#/bands/{{auth.profile.name}}/{{band.id}}">
My problem is, when I try to scroll the list up and down, it always shows blur on the selected list, and it makes the view when doing scrolls is not smooth enough.
I can solve that blur problem, but I lose the list ng-click and href capabilities, like
<ion-list show-Reorder="data.showReorder">
<ion-item class="item-avatar item-icon-right" ng-repeat="band in bands" type="item-text-wrap">
How to resolve that blur problem without losing ng-click and href capabilities, in order to make scrolls are smoother?
Try using ui-sref instead of href. If this doesn't work create an anchor link inside your ion-item and redirect through it. Hopefully this will solve your problem.
I have modal jqxWindow
<div id='jqxwindow'>
<div>Header</div>
<div>Content <div id='jqxMyCheckbox'>CheckBox</div> </div>
</div>
and I want to post control values from this window by HTML method.
If i add Form tags to the window, the jqxwindow seems to stop exists.
Please advice on right approach - how to Post control values from jqxwindow form.
please note, I'm looking for compact way, using declared controls only in HTML preferably. If i implement JQuery $.post method, I need to declare variables and control names again. That makes implementation too complex.
I hope following post will be helpful to you
http://www.jqwidgets.com/submit-form-with-jqxlistbox/
In brief, try to assign 'name' property to some of jqWidgets you would like to include in post.
I have a contentEditable div in a UIWebView. I want to disable the spell check feature.
Is there any API in the UIWebView ?
Thanks.
Have you tried this?
<div autocorrect="false" contenteditable="true"></div>
For me this works:
<div autocomplete="off" autocorrect="off" contenteditable="true" />
Please Check this. How can I disable the spell checker on text inputs on the iPhone
I'm implementing my own autocompletion on an <input> field inside a UIWebView, and the built-in keyboard autocompletion interferes with the user experience. Is there a way to use HTML or Javascript to signal to iOS that it shouldn't try to autocomplete?
In my comments I mentioned using the html attribute autocomplete but I tested it, and it doesn't address your issue. However, there is an attribute specific to Mobile Safari which may help. You could try turning off autocorrect like so:
<input type="text" id="your-field" autocorrect="off" />
I was wondering if anyone has seen this issue before.
I have two button on a webpage. When I navigate away from the page and hit the back button to return the value of one button is placed in the value of the other.
E.g
<input class="SmallData" type="submit" id="logButton" value="Log In" tabindex="93"></input>
<input class="btn" type="submit" id="acBtn" value="Detailed Quote"></input>
When I come back to the page Detailed Quote replaces Log In e.g.
<input class="SmallData" type="submit" id="logButton" value="Detailed Quote" tabindex="93"></input>
There is no JavaScript causing this to happen. I look at the source everything looks fine but I inspect the DOM I can see that the there is a different value.
Is there something about how web kit handles the dom that it gets corrupted when the back button is used?
Thanks,
Try giving each input element a name="some_unique_name" attribute -- see if that helps Safari differentiate.
Mght it be because of having two submit buttons...?
Just my "random" suggestion though... :)
Check if the same thing happens in Chrome (if you have access to a Windows box) to see if it's a WebKit issue or Safari itself.