Velocity 2012 Browserscope tests

[Rama A]

Hi,

The browserscope test below was presented today on a Velocity conference lightning demo presentation via 

http://goo.gl/KRGXR

When the presentation was run at realtime Android 4.0.3 stood out as the browser not supporting replaceState  but when I checked the test later there were 2 tests and the result was replaceState was supported!

Clicking on the "#tests" column link should normally lead to the detailed UA view but it has a null value being passed , anyway through browsercope's homepage I was able to resolve to the following URL

http://www.browserscope.org/browse?category=usertest_agt1YS1wcm9maWxlcnINCxIEVGVzdBiT554RDA&ua=Android%204.0.3

It was worth the effort as its fascinating that the HTC Sensation does not support history.replaceState but the Samsung galaxy SII does both being 4.0.3 ( rooted SII anyone?)

TL;DR: Browsercope considers 1 fail and 1 success as a success, I would think there should be a intermediate state or failure to alert authors.

Apologies as I do not recollect the presenters name mainly due to the immersive content, that was a great talk by the way and a great tip on the reliability of 4.0.3.

[Rama A]

It was Lindsey who spoke in the talk, "Doh" moment here..

[Lindsey Simon]

Hi Rama!

On Wed, Jun 27, 2012 at 3:34 PM, Rama A <vij...@gmail.com> wrote:

Hi,

The browserscope test below was presented today on a Velocity conference lightning demo presentation via 

http://goo.gl/KRGXR

When the presentation was run at realtime Android 4.0.3 stood out as the browser not supporting replaceState  but when I checked the test later there were 2 tests and the result was replaceState was supported!

 

Clicking on the "#tests" column link should normally lead to the detailed UA view but it has a null value being passed , anyway through browsercope's homepage I was able to resolve to the following URL

Oops, looks like I need to fix that link, thanks for bringing it up.

 

http://www.browserscope.org/browse?category=usertest_agt1YS1wcm9maWxlcnINCxIEVGVzdBiT554RDA&ua=Android%204.0.3

It was worth the effort as its fascinating that the HTC Sensation does not support history.replaceState but the Samsung galaxy SII does both being 4.0.3 ( rooted SII anyone?)

(elsigh stabs eyes with icepick)

 

TL;DR: Browsercope considers 1 fail and 1 success as a success, I would think there should be a intermediate state or failure to alert authors.

Yeah, that's a good point but I don't think worth changing right now.. It would be nice to be able to see trends of results next to the result which would make it clear that this one just needs more results to be definitive (it's why we have the sparse filter feature to hide rows with less than 4 test results)

 

Apologies as I do not recollect the presenters name mainly due to the immersive content, that was a great talk by the way and a great tip on the reliability of 4.0.3.

Glad ya liked it!

For those following along, the link to the talk is here: https://www.youtube.com/watch?v=RwvcjPE2Rm0&feature=player_embedded

 

--
You received this message because you are subscribed to the Google Groups "Browserscope" group.
To view this discussion on the web visit https://groups.google.com/d/msg/browserscope/-/0N_ENUken_oJ.
To post to this group, send email to browse...@googlegroups.com.
To unsubscribe from this group, send email to browserscope...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/browserscope?hl=en.

[Rama]

Thank you very much for responding, I was not sure the threaded view would work via email, so here goes.

"Yeah, that's a good point but I don't think worth changing right now.. It would be nice to be able to see trends of results next to the result which would make it clear that this one just needs more results to be definitive (it's why we have the sparse filter feature to hide rows with less than 4 test results)"

I agree, maybe something small like a different color or a "!" icon to indicate not to rely solely on.

http://caniuse.com/#search=replacestate , already has a note on this

Bottom line, dont trust it if your audience is Android.

I just got a Samsung galaxy SIII so will try that and post my results as well