Skip to content
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

Cross browser compatibility issues (formerly IE 11 display issues) #19

Open
4 tasks
matikin9 opened this issue Aug 15, 2017 · 22 comments
Open
4 tasks

Cross browser compatibility issues (formerly IE 11 display issues) #19

matikin9 opened this issue Aug 15, 2017 · 22 comments
Labels
Complexity: Medium Feature: Accessibility Issues that would broaden website accessibility feature: research plan any issue that is specifically about the overall research, not a subtask feature: research role: user research size: missing

Comments

@matikin9
Copy link
Member

matikin9 commented Aug 15, 2017

Dependency

#1898

Overview

We need to have our website be consistent on all browsers including government issued browsers so that our stakeholders can see our site.

Action Items

Original issue text

Some ahem government entities ahem are forced to use IE in their offices. It was brought to my attention that the page does not fail gracefully in IE 11. We should look into whether or not there is a simple fix.

@jjandoc
Copy link
Member

jjandoc commented Aug 23, 2017

Any screenshots? I imagine there's probably some CSS grid issues but I'm curious what else is going on.

@matikin9
Copy link
Member Author

image
image
image

@jjandoc
Copy link
Member

jjandoc commented Aug 23, 2017

Totes McGotes CSS grid

@jjandoc
Copy link
Member

jjandoc commented Aug 23, 2017

Some background here for whoever wants to address this. The screenshots in question are broken due to IE11's implementation of CSS grid. Check caniuse.com shows that it should at least be partially supported with an -ms- vendor prefix. We're using the PostCSS autoprefixer to deal with autoprefixing. IE might have its own implementation and syntax that requires a bit more attention than autoprefixing is providing.

@thekaveman thekaveman transferred this issue from hackforla/website-redesign Nov 18, 2018
@thekaveman thekaveman added the UI label Nov 20, 2018
@thekaveman thekaveman added the good first issue Good for newcomers label Nov 28, 2018
@ExperimentsInHonesty

This comment has been minimized.

@ExperimentsInHonesty ExperimentsInHonesty added the Discussion Starting point for gathering further information and/or feedback label Apr 23, 2019
@matikin9
Copy link
Member Author

Looks much better now, except there's a lack of space between the project cards. Also, not sure if this is intentional but the project cards are listed in a single column, as if for a mobile screen:

image

@ExperimentsInHonesty ExperimentsInHonesty changed the title IE 11 display issues Cross browser compatibility issues (formerly IE 11 display issues) May 1, 2019
@abregorivas
Copy link
Member

There are two major tools for cross-browser testing. However, there their trial versions are short and there may need to be a paid version that can be used across the organization.

@ExperimentsInHonesty

This comment has been minimized.

@ExperimentsInHonesty ExperimentsInHonesty added the HOLD Not ready to be worked on yet label May 2, 2019
@ExperimentsInHonesty

This comment has been minimized.

@abregorivas abregorivas self-assigned this May 9, 2019
@thekaveman thekaveman removed the good first issue Good for newcomers label May 22, 2019
@ExperimentsInHonesty ExperimentsInHonesty added UX and removed HOLD Not ready to be worked on yet UI Discussion Starting point for gathering further information and/or feedback labels Jun 1, 2020
@sayalikotkar sayalikotkar added the Feature Missing This label means that the issue needs to be linked to a precise feature label. label Jun 20, 2021
@ExperimentsInHonesty ExperimentsInHonesty added Feature: Accessibility Issues that would broaden website accessibility role: product Product Management and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role: design labels Jul 14, 2021
@ExperimentsInHonesty

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions github-actions bot added the To Update ! No update has been provided label Dec 10, 2021
@sacamp
Copy link
Contributor

sacamp commented Dec 12, 2021

Progress: Contacted ITA regarding browser usage
Blockers: Waiting on ITA response
Availability: 1 hour
ETA: Pending ITA response

@sacamp sacamp removed the To Update ! No update has been provided label Dec 12, 2021
@github-actions github-actions bot added Status: Updated No blockers and update is ready for review and removed Status: Updated No blockers and update is ready for review labels Dec 17, 2021
@github-actions

This comment has been minimized.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Dec 24, 2021
@github-actions

This comment has been minimized.

@sacamp
Copy link
Contributor

sacamp commented Jan 5, 2022

Progress: Contacted ITA regarding browser usage
Blockers: Waiting on ITA response
Availability: 1 hour
ETA: Pending ITA response

@sacamp sacamp added Status: Updated No blockers and update is ready for review and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Jan 5, 2022
@ExperimentsInHonesty

This comment was marked as outdated.

@github-actions github-actions bot removed the Status: Updated No blockers and update is ready for review label Jan 14, 2022
@github-actions

This comment was marked as outdated.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Jan 14, 2022
@sacamp sacamp removed their assignment Jan 19, 2022
@sacamp sacamp removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Jan 19, 2022
@jenjen26 jenjen26 self-assigned this Apr 13, 2022
@ExperimentsInHonesty ExperimentsInHonesty added feature: research plan any issue that is specifically about the overall research, not a subtask feature: research labels Jul 6, 2022
@ExperimentsInHonesty
Copy link
Member

Check the following emails to see where Simone sent the message from and add a checkmark to the one she used

  • [email protected]
  • [email protected]
    Check to see if there was a response. Either way, indicated here in a comment
    If no response, then we need to reach out to them again to ask what the oldest browser they support is
  • reaching out to [email protected] who is the chief data officer, to ask her who at ITA could answer the question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Feature: Accessibility Issues that would broaden website accessibility feature: research plan any issue that is specifically about the overall research, not a subtask feature: research role: user research size: missing
Projects
Status: New Issue Approval
Development

No branches or pull requests