Fixed z-index calculation error on IE11#1
Open
allenpiscitello wants to merge 56 commits intomasterfrom
Open
Conversation
Use a notation usable with XHTML
In IE11, the zIndex is returned as a number, which has parentsZIndex returned as an empty array. This empty array has a max value applied, which is -Infinity, which causes the zIndexOffset to not be applied. Chrome and other browsers accidentally get correct behavior since the zIndex property is returned a string, which makes !== 0 return true. To unify the behavior, I added parseInt to the comparison, and set a default value of the parentsZIndex to 0, so that the max value is always at least 0.
[Doc] Keyboard navigation is not supported for embedded / inline type
Occitan : spoken in South France, North Spain and Italy, and Monaco.
Added Sinhala (si) locale
Occitan locale
just a little change, it's uèi and not ùèi.
Occitan version update
[l10n]Add breton translation
resolves bug on days when DST is added.
Make XHTML happy
adds `updateViewDate` option
Removed reference to stefan petre's
* Adding Canadian English locale file Adding Canadian English locale file * Fixed missing EOF CR
Fix typo in month name
…ased on the defaultViewDate option
…shows-wrong-month Improve defaultViewDate documentation
…ate-multiple-dates Add notes about multiple dates and examples for update method
Added missing basque language properties
Week starts on monday in Slovenia
Added weekStart to slovenian translation
Fix placeholder
add monthsTitle
Add Code Of Conduct
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In IE11, the zIndex is returned as a number, which has parentsZIndex returned as an empty array. This empty array has a max value applied, which is -Infinity, which causes the zIndexOffset to not be applied.
Chrome and other browsers accidentally get correct behavior since the zIndex property is returned a string, which makes !== 0 return true.
To unify the behavior, I added parseInt to the comparison, and set a default value of the parentsZIndex to 0, so that the max value is always at least 0.