I added a Pulse patch but it doesn't allow me to click on or off in the checkbox, it's greyed out. please help?
From the information you shared, I'm assuming a hypothesis that you have a Pulse patch that has some kind of input attached at the On/Off input and this probably is why you can't click at the checkbox to turn it on or off.
Related
In my Blazor application, I have implemented a card-flip on mouse click. Now I wanted to add the edit functionality, that is as the user clicks on Edit button they enters in edit mode and can edit the card contents directly from the UI. Any lead on how can I achieve it, would be helpful.
Here is the code BlazorFiddle
You could start by creating 2 templates for your front and back card layout, one template for Display and one template for Edit, then you could toggle visibility on those templates on an event and copy new values to replace the original ones when the event is fired to exit the Edit template or binding to an object/properties.
Check my take on your code using the binding option.
Also changed the flip event to a double click so you can click the inputs without flipping the card, it's still a little buggy for me, I can only click on the input in some areas of its end, other areas seems like the 'card back' div gets in the way, but I think it's a start so you could try out something on that line of thought and/or fixing those other issues.
https://blazorfiddle.com/s/dvz9ppon
Please help!
Recently (probably with version 66), Chrome began displaying its autocomplete-suggestion drop-down on the initial mouse click into a search field instead of waiting until a character is typed.
How do I make Chrome go back to not displaying suggestions until I begin typing?
I have always made use of Chrome's suggestions drop-down for search fields, but I don't want or need to see a list of random suggestions just because I've clicked into an input field. I only want to see suggestions that match what I start to type (which is how it always worked until recently).
I tried disabling the "Single-click autofill" flag and even the "Show autofill predictions" flag as well, but these flags don't seem to affect the situation. Perhaps the term autofill in these flags doesn't refer to the same thing?
If anyone can help me with this, I'll be your best friend forever and ever!
Thanks for reading this.
I was having the same issue recently with a datepicker input. To get around it, I wrapped my inputs in a form and set autocomplete="off" in my form tag, as Chrome only recognizes that property for forms and not individual inputs. I added a keyup event so that if the input has text in it, autocomplete is re-enabled:
if (val.length > 0) {
$('#myForm').attr('autocomplete', 'on');
} else {
$('#myForm').attr('autocomplete', 'off');
}
You can also add an onBlur event to disable autocomplete suggestions each time you leave an input.
Apologies for the title-gore. We discovered today that clicking near the perimeter of the "up" arrow on an HTML5 number input will trigger an event on the "up" arrow on the first click, but trigger events on the "down" arrow with every subsequent click.
Here's a one line fiddle that demonstrates the issue. I am able to reproduce the bug consistently in Chrome 59.
<input type="number" />
Move your cursor to the top edge of the number input's "up" arrow and click several times. It may take a few tries to get the cursor in the right place. The first click will trigger the up arrow, but every subsequent click will trigger the down arrow.
Is this caused by some type of click event fuzzing done by Chrome in an effort to assist with extremely minor misclicks? I'm pretty lost here.
Note: I attempted to reproduce in Edge and Firefox but was unsuccessful. This may just need to go to the Chrome team.
This is a bug. You can report it at https://bugs.chromium.org if you like.
The gist is this: The code linked to below contains logic like
if (is_pressed) {
if (spin_up_pressed) {
highlight spin up
} else {
highlight spin down
}
}
Which is evidently not entirely correct.
https://cs.chromium.org/search/?q=spin_up%7CSpinUp+f:theme&type=cs
I am constructing a card-game (for tvos) where the user should be able to remove cards from a board.
At the end of the game only a few cards may be left at the board, and they might e.g. be arranged as the buttons in the picture below.
How can I let the user move focus from say button 1 to button 0 or 2?
In un-accepted answers to a similar question at SO, it was suggested that one should use an UIFocusGuide. I do not think that answer is applicable to my problem, because in that approach one must tell the focusGuide the preferredFocusedView in advance (e.g. before the user swipes in siri-remote)! In my case, the preferred next focus depends on the swipe direction, e.g. the focusHeading.
UIFocusGuide is the applicable way to handle this issue, and it is possible to assign each focus guide a preferredFocusedView in advance of knowing which direction the user would move (based on which button has the initial focus).
For example, here's a solution for your edited example that shows how it's possible to move the focus from focused button 1 to either button 0 or to button 2.
If the user swipes up or left, the focus would move into one of the green focus guides, which would change the preferred focus view to button 0.
If the user happened to swipe down or right from button 1, the focus would move into one of the blue focus guides, and button 2 would become focused.
As the focus changes, you update the focus guides to guide the focus back in the return direction. For example, once button 0 gained focus, you would update preferredFocusedView for the green focus guides to prefer button 1, so the user could then move down or right from focused button 0 and end up back at button 1.
Just keep in mind that you only need a focus guide if the Focus Engine can't determine the next view. You should test different scenarios to determine when a guide would actually be required.
I am trying to get my search boxes to change a different colour on click but at the moment it only changes colour for the duration of time I am holding down on my mouse. As soon as I let go of pressing down the cursor it changes back. How do I make it so it changes colour but as soon as I click something else on the page (even whitespace) it changes back to the original colour?
Take a look at this:
http://jsfiddle.net/LPVfn/
Cheers!
James
use
.search:focus
instead of
.search:active
There is a js library called HoverIntent. Maybe you could use it to get the desired effect.
http://cherne.net/brian/resources/jquery.hoverIntent.html
I'm currently using it to delay displaying a div tooltip for a few milliseconds after the user hovers over the search box.