amazon has a problem with a small handful of style placements, like 5 out of hundreds. When it bails out with a runtime, it neglects to process others that might be able to do successfully. This might be true for other sites besides amazon too.

What do you think of the idea of wrapping
if(!t.style[propname])
t.style[propname] = propval;

in a try-catch block?

Note about the root cause: Diagnosing the root cause would be another way to go. I think the cause has something to do with form options. querySelectorAll("#navbar #nav-search .nav-search-dropdown") reports that the length of the resulting set is 1, yet if you echo it from jdb, there are about 50 elements in the resulting set. And it can't get a handle on .style for some reason. It seemed like, given result set rs, rs.style did not exist, and rs[0].style did not exist,
but
rs[0][0].style did exist. After I put some time into diagnosis, I thought "this is taking a while for one style... if the issue is obscure, we could just skip a few by using try-catch.." As we do currently
with a few pseudos.


_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev

Reply via email to