Skip to content

[Input Date Picker] - calendar dropdown is not displaying on top of other content - Safari only #13795

@DintaMel

Description

@DintaMel

monday.com sync: #11121083862

Check existing issues

Which Component

Input Date Picker

Actual Behavior

In Safari, the Input Date Picker is obstructed by other content. The dropdown values of the month/day/year are not visible until selected.

In Modal:
Image

In Shell
Image

Expected Behavior

I expect the calendar dropdown background to be opaque and to be able to see the dropdown values, similar to how it shows in chrome.

Image

Reproduction Sample

https://codepen.io/DintaMel-the-lessful/pen/RNRxjqa

Reproduction Steps

  1. Open codepen in Safari
  2. Select Open button
  3. Select dropdown for date
  4. Observe issue

You can also view the issue outside of a dialog in this codepen.

  1. Open codepen in Safari
  2. Select Layer effects block
  3. Select date input dropdown
  4. Observe issue

Reproduction Version

5.0.0-next.81

Relevant Info

This is in Safari only. Edge, Firefox, and Chrome are all displaying correctly.

Regression?

4.0.0-next.28

Priority impact

impact - p1 - need for current milestone

Impact

Date picker in Safari is difficult to use without changes since users can't see all the values.

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-react
  • @esri/calcite-design-tokens
  • @esri/calcite-ui-icons
  • @esri/eslint-plugin-calcite-components

Esri team

ArcGIS Online

Metadata

Metadata

Assignees

No one assigned

    Labels

    ArcGIS OnlineIssues logged by ArcGIS Online team members.bugBug reports for broken functionality. Issues should include a reproduction of the bug.c-input-date-pickerIssues that pertain to the calcite-input-date-picker componentcalcite-componentsIssues specific to the @esri/calcite-components package.estimate - 3A day or two of work, likely requires updates to tests.impact - p1 - need for current milestoneUser set priority impact status of p1 - need for current milestonep - mediumIssue is non core or affecting less that 60% of people using the libraryregressionIssues that are caused by changes in a release, but were working before that.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions