@labs20 said in [v1] QSelect Cant trap ENTER key:
Yes, now I found it.
And it works indeed, but not for @keypress.enter.native.
For @keyup.enter.native it works just fine.
yeah wrongly stated it in my first post sry, it’s @keyup in the actual code since onkeypress is actually deprecated.
mmmm… I really wish that was not implemented. I’m trying to catch the enter keystroke at the q-select with no luck.
I need to catch when the user hits the enter key and branch to a few paths depending on some factors present at the form. But while I can successfully catch ESC key for example, ENTER keep failing.
Any help? Is the q-select preventing it to bubble?
Today, I face the same issue, whatever I retry many times, it still appears the following words:
Running @quasar/cli v1.0.0-rc.2
$ quasar <command> <options>
Help for a command
$ quasar <command> --help
$ quasar <command> -h
–version, -v Print Quasar CLI version
create Create a project folder
info Display info about your machine
(and your App if in a project folder)
upgrade Check (and optionally) upgrade Quasar packages
from a Quasar project folder
serve Create an ad-hoc server on App’s distributables
help Displays this message
=> IMPORTANT !
=> Trigger this inside of a Quasar project (and npm/yarn install) for more commands.
My operation system is MacOS and I don’t know why still now!
Solved. The problem with the footer becoming un-anchored was apparently caused by our partner’s website, which was set to rotate to landscape mode. When they changed their setting, the problem disappeared.
We created an absolutely positioned div “off screen” anchored to the top of the viewport, that would provide a black background under the status bar area of X-series iPhones (for other reasons we had to make the status bar transparent). The redirect was un-anchoring that div. The solution was to move the anchor point so at least part of the div was on-screen (I used 100vh - 10px, anchored to the bottom of the screen. The div had a fixed height that extended above the top of the screen). Including here for reference in case anyone else has a similar issue.
@s-molinari @digiproduct, Thanks for the replies. I solve my issue with Qspace with the help of the the guys in the discord chat. I thought that implementing this kind of feature was a easy task, just using one the many alignment class available in the framework, still don’t know if I was doing something wrong or the toolbar containter has some black magic that I dont know about it.
No. You can work with Unix timestamps, you just have to reformat the timestamp to a format the component will work with. The formatting Razvan linked to is for formatting the text output of QInput (which you’d need for making your custom date/time component).