1357747 - Add screenshot showing visual difference in text-rendering examples, from browser where there is a difference

Status: RESOLVED WONTFIX

(Developer Documentation Graveyard :: CSS, enhancement, P3)

Description

[mh]

What did you do?
================
1. Read the documentation
2. Looked at the screen with a magnifying glass
3. Checked the display in jsFiddle
4. clicked on Feedback
5. checked oput every option that seemed relevant (2 only)
6. signed up for an account (!)
7. read the send feedback page - not much help
8. gave up but wrote this anyway (fwiw)

What happened?
==============
1. Read the documentation .. that's that ereally
2. Looked at the screen with a magnifying glass .. can't really addanythi9ng here
3. Checked the display in jsFiddle .. and it didn't help i.e it also looked the same as the page

ok, this seems pointless .. so, onwards.

What should have happened?
==========================
A. On the page at https://developer.mozilla.org/en-US/docs/Web/CSS/text-rendering some examples are given of the effect of text-rendering: optimize legibility.
B. The "examples of difference" are identical i.e they show no differences.  This is true both of the browser display of the page and the display in e.g jsFiddle
C. what should have been the case is that the examples should have looked different i.e showing the difference between using/not using the code.

Is there anything else we should know?
======================================
You could make your site more accessible.  I'm really struggling here just to provide some feedback, and I know it'll probably be ignored as it is still in the wrong place, wrong format etc - but without spending even more time that I already have to date .. this is the best I can find to do here.   Which yes is bonkers.  What about e.g a simple feedback form?
Other than this though, love the site.  Thanks !

Comment 1

[John Whitlock [:jwhitlock]]

Thanks for your feedback, and thanks for describing how you got to writing a bug.  There is a menu "Feedback -> Report a Content Problem", but it failed since it wasn't the obvious path for submitting your feedback.

The Browser Compatibility table claims that this is not a widely supported feature:

https://developer.mozilla.org/en-US/docs/Web/CSS/text-rendering#Browser_compatibility

caniuse shows wider support, but still shows some browsers as not supported:

http://caniuse.com/#feat=kerning-pairs-ligatures

This suggests the page could be enhanced with screen capture from a supporting browser.

What browser and OS did you use for your tests?

Comment 2

[mh]

Hi, apologies for the delay in my replying.
I'm using FF 40.0.3 and Win7.

Is it possible to attach a screenshot (e.g here) showing what the page coding should gernerate?

"Feedback -> Report a Content Problem" - thanks.
D'oh!  No idea why I didn't see this.  Was sure I'd clicked that option. Aplogies :(

Thank you for the links.  I'd thought the support was ok/worth addressing but need to rethink!

Comment 3

[John Whitlock [:jwhitlock]]

Yes, you can start by clicking "Attach File".  I'll attach my screenshots for macOS 10.12.

Comment 4

[John Whitlock [:jwhitlock]]

Attachment: auto20px-Firefox53-macOS10.12.png

No visible difference on Firefox 53 on macOS 10.12

Comment 5

[John Whitlock [:jwhitlock]]

Attachment: auto20px-Chrome57-macOS10.12.png

No visible difference on Chrome 57 on macOS 10.12

Comment 6

[John Whitlock [:jwhitlock]]

Attachment: auto20px-Safari10-macOS10.12.png

No visible difference on Safari 10 on macOS 10.12

Comment 7

[John Whitlock [:jwhitlock]]

Attachment: speedVsLegibility-Firefox53-macOS10.12.png

No visible difference on Firefox 53 on macOS 10.12

Comment 8

[John Whitlock [:jwhitlock]]

Attachment: speedVsLegibility-Chrome57-macOS10.12.png

No visible difference on Chrome 57 macOS 10.12

Comment 9

[John Whitlock [:jwhitlock]]

Attachment: speedVsLegibility-Safari10-macOS10.12.png

There is a visible difference between optimizeSpeed and optimizeLegibility on Safari 10.1 on macOS 10.12

Comment 10

[BMO Automation]

MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.