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

Remove reference to Internet Explorer in report_bad_page.php #1141

Open
70ray opened this issue Mar 12, 2024 · 2 comments
Open

Remove reference to Internet Explorer in report_bad_page.php #1141

70ray opened this issue Mar 12, 2024 · 2 comments

Comments

@70ray
Copy link
Collaborator

70ray commented Mar 12, 2024

Since we no longer support IE.

What should we replace this list item with? Since I've never encountered this problem I don't know what to suggest.

@bpfoley
Copy link
Collaborator

bpfoley commented Mar 12, 2024

To me, it sounds like the example in text is referring to intermittent issue that might occur due to an unreliable/slow internet connection -- the browser gave up on loading the image because of a timeout. It doesn't sound like a browser-specific problem at all.

"Sometimes, the image may not show up due to technical problems with your browser. Depending upon your browser there are many ways to try to reload that image. For example, in Internet Explorer you can right click on the image & left click Show Image or Refresh. This 90% of the time causes the image to then display."

Since we're talking about IE:

  • faq/feeds_sdk/index.php has an out of date reference to IE which is irrelevant to us since we don't support it.

  • tasks.php has a very arbitrary $browser_array and $os_array with ridiculously out of date entries. We really need a schema change to turn these into free-form text fields (even if we keep a list of suggested OSes/Browsers to autocomplete (or autodetect from the User-Agent) when creating new tasks.)

@srjfoo
Copy link
Member

srjfoo commented Mar 13, 2024

Since we no longer support IE.

What should we replace this list item with? Since I've never encountered this problem I don't know what to suggest.

Several years ago, a couple of the db-req squirrels looked at report_bad_page.php and thought that we should rewrite those instructions completely. We got distracted by more immediate tasks and never got it done. Judging from the fact that some people apparently think every intentional blank page is a bad page, I'm not sure how many people actually read those instructions. And that first paragraph, I think needs to be totally rewritten. What it's describing is not what we expect of proofreaders nowadays.

I agree with Brian about removing IE from other places on the site, but I think that's a separate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants