I have noticed that if a VScrollBar component contains RichEditableTextFields then when I am scrolling the component, and the mouse falls over a text field, then the component stops scrolling because the mouse cursor has changed and the mouse focus is on the text field. (even though I haven't given focus to the field by clicking on it).
This feels pretty buggy and I'm wondering if there is a way around it?
Edit: I should add that this only happens on Mac OSX when using the touchpad.
This has now been fixed in the 4.6 SDK. The workaround is to update your SDK version.
Related
I'm creating this toggle component but as you can see in the gif whenever I press it on a mobile device there's this flashing shadow behind it, which is probably some native behaviour to indicate the button is being pressed.
I'm trying to get rid of it as it makes the component look kinda clunky and not very smooth. I tried several combinations of props like changing the background color, shadow, transitions, pseudo selectors like :active and others, even changing the element from <button> to <div>, nothing really works and I couldn't find a solution for this anywhere.
Thanks in advance for any help!
I have a spinning wheel animation performed while opening a modal=true p:dialog. (via ajaxStatus listener). When dialog frame is showed up it keeps spinning because there are still some computations being executed required to display dialog content. This is OK.
But! If click somewhere on the dialog the wheel disappears. Actually it is being covered by the dialog as its z-index becomes less.
I tried explicitly set z-index in dialog style to 9999 but it doesn't catch it up. Moreover I found that z-index is being dynamically changed when focusing dialog or wheel. So even if I set it to 9999 via browser dev tools, it eventually (in some time) will be set back to its previous "covered" value.
Is there a way to set and fix z-index of a spinner (which is a nothing but a transparent dialog) ?
Thank you!
I have reviewed a few articles about using CMFCButton but I still have a question.
My button has a image on the left and a caption on the right. There is nothing fancy, except I am using WindowsBlinds 10 on my computer (I have deactivated it and the issue remains).
With regular buttons they highlight when the mouse is over them. But this is not so with the CMFCButton. The best I came up with is to set the style to SemiFlat.
Mouse not over control:
Mouse over control:
If I set the style to Style 3D then you see no change at all whether the mouse is over the button or not.
Why is the CMFCButton not following the rules? Is there a setting? I don't want to use owner drawn.
Based on the comments provided I have changed to a CButton as that renders as I need out-of-the-box!
I am creating a simple mobile app with Cordova. For good user experience I would like there to be instant feedback whenever a user presses a button. This should be accomplished with the :active pseudoclass. It mostly works, but it's not quite 'instant'.
See the jsbin here.
With desktop Chrome, clicking the button produces absolutely instant feedback, no question.
With Chrome for Android, tapping the button quickly feels pretty quick, but a slow tap or holding on the button causes a delay (it might be hard to notice, but it is there and it's bugging me).
I think this is something to do with scrolling. If you go to the Android settings, there is a scrolling list of options. These options seem to highlight with a similar delay. However, any native Android buttons which are not within a scrolling list are absolutely instant (for example, the back button in the top right, or save/cancel on a popup dialog).
Is there some way I can convince Chrome that these buttons are not on any kind of scrolling pane and should just be highlighted instantly?
This is probably unrelated, but I have also noticed that holding on an html button highlights it, but then moving your finger (still within the button) causes the highlight to disappear. This does not match the behaviour of native Android buttons, which would stay highlighted so long as you stay within the button.
Edit: I should add that -webkit-tap-highlight-color (which only works with cursor: pointer) is a bit faster than :active, but it's not an acceptable solution, for a few reasons:
The highlight disappears if you hold on the button for more than one second
It clashes with :active - to get sensible results with -webkit-tap-highlight-color you would have to remove :active, which makes no sense
There is no way to control the size/shape of the highlight, which might not match the actual button (sometimes it bleeds around the edge, or has mismatching rounded corners)
The correct HTML way of solving this is :active, and I would like to use that if at all possible.
It seems the best way to solve this is to listen for touch events and set a class:
$('button').on('touchstart', function(e){
$(this).addClass('active');
});
$('button').on('touchend', function(e){
$(this).removeClass('active');
});
To keep this as closely related to the :active pseudoclass, I opted to use a class of active and add styles for both like this:
button:active, button.active {
// active style
}
For more information, see: http://samcroft.co.uk/2012/alternative-to-webkit-tap-highlight-color-in-phonegap-apps/
I am using javafx 2.2 for my desktop application.
The problem I am facing is that when I hover on the buttons some of the part of text gets hidden. The problem is only on some of the machines. Attached is a screenshot of the save button. The text (Save) gets hidden when I focus or hover on the button.
I tried removing the button: hover CSS but now when I click on it, then I get the issue.
I tried removing the button: hover CSS but now when I click on it,
then I get the issue.
Its hard to diagnose the cause with no code provided, however given that by removing the hover styling you removed the behaviour on hover, have you also tried removing the :focus and :active classes? These are typically assigned during a click event.
What you may also want to do is take the hover class you removed, look at the properties and remove each one at a time to find the culprit- if this doesnt work there is likely some other runtime manipulation of the element happening, it'll be impossible to chase up without code unfortunately.