How to present different result regarding to different web browser

[Jeffxz]

How to present different result regarding to different web browser

[dlazin]

I think this is addressed by @iherman 's comment #102 (comment), and thus by your #105 (which implements his suggestion correctly).

Is that sufficient (so that we can close this issue), or am I misunderstanding some subtlety?

[iherman]

I think this is addressed by @iherman 's comment #102 (comment), and thus by your #105 (which implements his suggestion correctly).

👍

[Jeffxz]

Thanks @dlazin. Yes lemme close this one.
Also, in today's CG meeting you mentioned there might be some candidate for test cases to implement. Can you pls point me where I could find it? I think can get some time to write some test. Creating test contents is also fun!

[iherman]

Thanks @dlazin. Yes lemme close this one.
Also, in today's CG meeting you mentioned there might be some candidate for test cases to implement. Can you pls point me where I could find it? I think can get some time to write some test. Creating test contents is also fun!

I do not think we have an explicit list (I may be wrong on that). However, a neat trick is as follows. If you go to the editors' drafts of a spec, say, the RS spec, for a number of MUST statement (say, in https://w3c.github.io/epub-specs/epub33/rs/#sec-pub-resources) you will see a small pull down menu denoted as 'tests'. Those refer to the number and the links to the tests that are already existing. You may of course choose some additional tests, but better look for sections, functionalities, etc, in the text that does not have such tests but that should (at the end of the day, the goal is to have at least one test for each MUST statement).

B.t.w., https://w3c.github.io/epub-tests/contributing is your friend on how to write a test...

Note also that I will merge, hopefully later today, #100, which includes a number of tests on the scripting environment. Once there, I would be very interested to see how your implementation fare with those!

[Jeffxz]

awesome. Thanks @iherman. lemme read through. Some items I might be able to help write test that wysebee can use as well.