This repository has been archived by the owner on Jan 30, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 282
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix input field width in google chrome
- Loading branch information
1 parent
c72d1a4
commit 78aa7c4
Showing
4 changed files
with
17 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
78aa7c4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to have caused a horizontal scrolling issue... The quickest fix I can see would be to use
calc(100% - 125px)
as the value... Ideally it would have['required' => 'required', 'class' => 'input-width']
and then apply it to the.input-width
class in the CSS... I haven't got a workflow put together for contributing yet, but would like to soon...78aa7c4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Totally valid issue. Would you like to help us to rewrite the whole form layout? I'm thinking about making it properly like bootstrap or foundation does it but it's quite a lot of work just to fix it.
78aa7c4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@simonschaufi, I made a pull request here for it: kimai/kimai#1265
And I'd totally like to contribute development to Kimai. Was thinking that perhaps I will ask if my job will sponsor work on it (if they decide to adapt Kimai which I think is feasible). I think that'd be a cool situation, and actually made the pull request while spinning up a test site for us to try :)
78aa7c4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If they don't use it yet, consider starting with v2 directly:
https://www.kimai.org/blog/2018/kimai-v2-announcement/
78aa7c4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kevinpapst I did look into that in detail. I'd used Kimai v1 for years freelancing, and did an extensive test with v2 for some time recently. I can see where I might have made the jump for freelancing, but at the moment v2 is missing some things that would keep us from being able to hit the ground running. Specifically, granular control for user access would be important, and I think that v1 does that pretty well... It's awesome that the data from v1 can be imported into v2, so we'll be able to make a transition at some point. My recommendation has been to go with v1 for the foreseeable future, and keep an eye on v2...
78aa7c4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your feedback @groovenectar !
One wish: please leave such feedback in the v2 issue tracker, so I know what can and needs to be improved to get further adaption in companies.