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

Incorrect "tip" in text transform tests #13505

Open
frivoal opened this issue Oct 14, 2018 · 7 comments
Open

Incorrect "tip" in text transform tests #13505

frivoal opened this issue Oct 14, 2018 · 7 comments
Assignees

Comments

@frivoal
Copy link
Contributor

frivoal commented Oct 14, 2018

As discussed in https://bugzilla.mozilla.org/show_bug.cgi?id=1498148#c40, a bunch of text transform tests give the suggestion to copy and paste the result of the transform to in some unicode tool to check if the correct characters have been produced. However, text-transform is not supposed to affect copy and paste, so that's wrong, and that "tip" should be removed. Maybe also the tests that cannot be evaluated without relying on that tip, if any, should be rewritten.

@dpino
Copy link
Contributor

dpino commented Oct 14, 2018

Besides the copy & paste trick, the tip also states that:

"To identify the characters where differences occur, in order to report problem characters,either mouse over to reveal a tooltip"

For this reason many tests have a title attribute in an span element. However, at least in the browsers I tested (Firefox and Chrome), when I hover a glyph or character the title's tooltip doesn't show up.

Thus, should this part of the tip be also removed, or should it be fixed somehow?

@dpino
Copy link
Contributor

dpino commented Oct 14, 2018

It seems the tooltip indeed shows up when opening the test in a browser using the web-platform-test tooling (wpt serve). However, tooltips don't show up when launching a test using Firefox's mach wpt. So this seems to be an issue on Firefox's tooling I suspect.

@r12a
Copy link
Contributor

r12a commented Oct 16, 2018

There are two reasons i think we should keep the tip:

  1. The suggestion to copy into a tool for identification is not expected to rerun the test, it's simply a way of finding out what characters are in the code. So the advice remains valid.

  2. I develop these tests for use in the i18n test suite and then copy them to WPT. I try very hard to make tests work both for people who use WPT and in the i18n context, so that it's easy to track changes between the two storage locations, and identify substantive changes that need to be applied to the other location. I would strongly prefer that people do not tidy up non-susbtantive aspects of the tests in WPT, because if you do change 138 files there, and the files come out of synch, it can become it difficult to assess what changes need to be back-ported to the i18n test suite files. I don't think the notes in question are problematic (and in fact, originally they were visible to the tester, but i made them into comments to better follow the WPT expectations), and they are there to help people who run the tests manually in the i18n context. I therefore would prefer not to fiddle with the files.

It's hard enough to find the time at the moment to port the tests we have to the WPT environment (we still have probably several hundred waiting to be copied over), so i'd like to avoid things that will increase the difficulty. (Of course, substantive errors or problems are good to change. I'm just talking about unnecessary edits.)

@r12a r12a reopened this Oct 16, 2018
@frivoal
Copy link
Contributor Author

frivoal commented Oct 19, 2018 via email

@dpino
Copy link
Contributor

dpino commented Nov 5, 2018

I've been absent for the last two weeks so I wasn't able to reply earlier. Sorry about that.

I'm fine with reverting the changes or updating the tooltip message as @frivoal suggested. If you prefer the latter I can prepare a new PR.

@frivoal
Copy link
Contributor Author

frivoal commented Nov 12, 2018

@r12a: see previous comment. I'd prefer updating the message as suggested above. Is that OK from the point of view of the i18n group, and of keeping things in sync?

@r12a
Copy link
Contributor

r12a commented Sep 27, 2021

Gentlemen, i no longer have the bandwidth needed to maintain parity between the WPT tests and the i18n test suite tests, so please feel free to make whatever changes you'd like the tests in the WPT repo. If at some future point i work on the tests in the i18n repo, i'll consider adding something along the lines of @frivoal's suggestion (thank you).

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

No branches or pull requests

3 participants