![]() The value of doing so and the history of updates that has missed the mark from time to time in the past should be more than enough to influence the TS powers-that-be to consider what I am suggesting. We, your customers, can give you feedback such that it either confirms the update is good or that there are issues with screenshots/videos to substantiate what is found. Waiting for customer testing after you release a new update is putting the cart before the horse - full stop. Even as a band aid, for my use, it is way too slow, cumbersome and user-error-prone.Įxtra User Testing: Honestly, transparently, perhaps TS should consider giving some of us an opportunity to "beta/release test" a next intended release with a list of the changes to be tested. In of itself, Panoramic Capture could never be accepted to replace Scroll Capture for a whole suite of good reasons. ![]() If you review other threads here concerning scroll capturing, while panoramic capture does work - but, a BIG BUT, it is a band aid at best until the problem reported can be fixed. ![]() I would add this kind of problem from capturing such pages has historically haunted us with mixed results, at best. In further testing, yeah, any page with something dynamic on it can cause some kind of problem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |