In my default key bindings I have ctrl+/ for comment by default. But it only works if I press ctrl+; in my keyboard. Whats wrong?
Could it be that sublimetext is assuming a wrong keyboard layout?
Edit: It seems to be a keyboard conflict in some keyboard layouts.
Check some of the answers from this stackoverflow post. Some of the workarounds may apply.
Related
When a <select> field is focussed, pressing the Enter key does not submit the form. Is it possible to make it submit the form, without using JavaScript?
A solution working in quirks mode is fine, too.
It is not possible to alter this behaviour without using JavaScript. According to the discussion at this question, capturing the keyup event is the best option for browser compatibility.
You may want to reconsider altering this behaviour, as discussed at this question you may surprise your users by doing so.
I was unable to find the solution to this problem:
I use one in a webworks app. It's supose that this input will accept integers and float numbers.
The problem is: When I insert some data, for example 3.1415 the device removes the dot and inserts 31415.
I'm not using the input types inside a form so the "novalidate" option isn't possible.
I tried a lot of stuff to fix the problem. Any Idea?
Possible solutions(tricks):
- Use type = text and force the keyboard layout to be the numeric one.
- Disable the validation to this input (and no others).
Do you know how to do that? Do you know other solutions?
Regards. Pablo.
This is a know bug in Blackberry 10.
There are posts about it in their support forum, here is a link to one of them.
The only real way around it is to use a standard text input and validate the content yourself until this bug is fixed.
I just tested this on an internal build (10.2.1.x) and it is working prefect for me although I'm unable to track down a specific OS build number where the fix was implemented.
I'm trying to figure out which html elements have a default action that can be prevented by calling preventDefault(). I cannot find it in the specs. Where is it specified?
In a nutshell:
preventDefault() makes it such that any action(s) that would happen, if the javascript was turned off, are suppressed/blocked.
All the rest I could mention is already mentioned by the other answers.
I'm not entirely sure it's specified, though I imagine it is; but default actions seem to result from user-behaviour/-interaction; so a rule of thumb would be: 'if a use can interact, and do something, with this element there's probably a default action expected of this element/interaction.'
Though I can't cite a source for this supposition as yet, unfortunately.
On Chrome and Firefox, a form is submitted if the return key is pressed inside any text input inside the form.
Is this behaviour part of the standard?
Yes, this is default behavior.
[edit] I should qualify, this is for pretty much everything IE7 and up. I do know that some older browsers (Netscape) may not have done this. But for today's browser landscape, yes this is standard.
No, this behavior is not required. I’m afraid it isn’t even mentioned in the HTML 4.01 specification, though this is probably just an oversight.
But it is very common behavior and needs to be taken into account: users may well accidentally submit form data by pressing Enter, when they still intended to continue filling it out.
There are some browser differences, e.g. IE 9 does not do anything when Enter is pressed in a field provided that a) there are more than one text input fields there and b) there is no submit button. On older versions, condition a) was sufficient, and this was more or less the original idea (the feature was meant to make it easy to use very simple search forms without causing confusion).
I have the known issue with wmode transparent and input textfield in my page.
I know that the question is often asked but I have a special situation with that case.
I need to embed my swf with wmode=transparent but in my swf I have an input textfield and the bug with "#" or "." symbols exists.
I have a french keyboard and I decided to overcome this problem with a string replacement with the FirefoxWmodeFix class from Manmaru (see the link below).
http://www.manmaru.fr/mlab/?p=95
It works for my keyboard but I need that "trick" with EN/DE/IT keyboard.
Could anyone help me with the right combination of keys on different keyboard and different OS system to display "#" and "." symbols.
I don't have any foreign Windows system to get the key code for each combination.
Or if anyone has another solution, I will be pleased to hear that one.
Thanks in advance for any help.
wmode transparent is a known source of countless bugs -- specifically affecting proper text rendering. If you solve (hack your way around) this one, you will find more. :(