I'm using the Bootstrap 4 datepicker for my web app which I primarily implemented looking at the behaviour in Chrome. Everything works fine there i.e. all the dates are pickable and I only have set a predefined date range that a date is pickable from.
However, now that I've finished implementation based on Chrome's behaviour, I came to realize that none of this is working in Firefox. That is I cannot pick any date at all when the calendar opens up. All the dates are deactivated and not clickable.
I have tried to find the reason for this through a google search but cannot find anything related to this problem.
Any idea why this is happenning and how to fix it?
Related
It is very difficult to program when you are trying to inspect an element, say:
Then you refresh the page, and chrome throws you back to:
Forcing you to open the path all over again.
Not very nice or productive use of my energy.
Now, I have mentioned this in the past and even filed a bug report and I remember it being taken care of at one point, but it seems to be back now. I can not find the old info to link to.
All chrome has to do is reselect the previous selected element after a delay ( which I assume must be defined statically in order to guarantee that at that time the element do exist again).
Ideally, chrome dev tools would allow us to programmatically allow us to select any NODE to do this selection programmatically, but i don't think we will get there.
This is very frustrating to deal with.
Any tips? Is this possible in other browsers? Firefox, firebug, safari?
While debugging, sometimes I get stuck finding the correct event, but recently I found out that Firefox indicates you all the events of an element and their code, I wonder if there is something similar in Chrome. I know that maybe Developer
Tools would have something like that, but I don't understand this a lot, and with Firefox I have all the events very fast.
Here are a few pics of what I mean. I cannot upload images because my account is new.
https://ibb.co/5W2M3TT
https://ibb.co/4T8rWc1
https://ibb.co/4YWzRv3
https://ibb.co/LQVxst1
HTML Select Input Dropdown is not getting dismissed properly on iOS 11. Upon closing the dropdown, an empty dropdown with blank options reappears in its place.
Nothing has changed, and we started getting complaints from iOS users, we could not replicate. Updated iOS to latest and now can replicate. The issue is, that they are always blank, from then on.
Pressure has been put on us to resolve this issue, has anyone came across this issue and have a workaround to resolve?
This is a cordova application, jQuery, bootstrap and knockoutjs. Any help be appreciated. I know it may be vague and no code but this is basic html selects.
Update to ios 11.2 and issue has been resolved. After reading plenty of news articles this was nothing compared to the list of bugs that went out on this version.
Stumbled across this weird behaviour when I was working on the search for our site.
When I was using the search on our site, i would get no matches for results that I knew definitely existed. When I retyped it, the input field history showed my search in a different font.
Typing the search from scratch would return the correct results. But when I clicked the history item with the weird font, it would still show no results.
What caused this to happen? I don't have any other language enabled on my pc...
I'm developing a web app which uses HTML5 time fields that is intended for use on both desktop and tablets. The time fields work fine for both Chrome and Safari on desktop, displaying '--:--' as a default value with arrows to increase/decrease time as I'd expect.
The issue is when testing it on a Nexus tablet it seems to add an AM/PM option which defaults to 'AM' that isn't present at all on the desktop versions. My issue is sometimes these time fields aren't used strictly for inputting a time but also sometimes for measuring the duration of something, where an AM/PM option simply wouldn't make sense.
I've tried Googling for a solution to this problem but I have not been able to find very much information regarding it. Does anyone know why this occurs and how I can turn it off? Is it a system setting on the Nexus or is there an attribute I can add to the time tags to prevent it?
Well I seem to have found the issue myself - the system's language setting was 'English (United States)' which seems to overwrite setting time to a 24-hour format. By changing the language setting to 'English (United Kingdom)' it now obeys the 24-hour format and AM/PM no longer shows in the time fields.
It's pretty annoying that a system setting has to be changed for this rather than being able to do it on a site-by-site basis, but fortunately for this project I do have control over system settings by and large so it has solved the issue for me.