-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update outdatedbrowser.js #232
base: develop
Are you sure you want to change the base?
Conversation
Tolerate absence of btnClose and btnUpdate, when using custom content.
@schonarth thanks 👍 |
My client is very specific in how they want the message bar to appear, While I was at it, I also covered the same condition for the Close button, Thanks for considering my small contribution =] Cheers Em ter, 26 de abr de 2016 às 05:54, Alexandre Gomes <
|
@schonarth Thank you 👍
We know that js is more prone to errors then css, and this way I know I don't need to test for older browsers (IE6, etc) because I am really sure it will work. Personally I would do this approach, so maybe we will wait for the merge if more ppl wants your approach. |
It works, though it changes the base logic. My point was to make the change as small as possible, just to avoid exceptions in my particular case. By all means, do as you prefer =] |
@schonarth let see what is the feedback of the community. |
@alexandre-works do we received any feedback from the community about this subject? |
@brunoamorim no. We had no suggestions or requests regarding this feature. Still thing that the CSS approach is the best solution for this. |
I just think that a null check is never too much for a more robust piece of Vc q sabe. Em ter, 11 de out de 2016 às 17:29, Alexandre Gomes <
|
Tolerate absence of btnClose and btnUpdate, when using custom content.