- From: Mark T <paradisaeidae@gmail.com>
- Date: Wed, 11 Mar 2015 10:26:20 +1100
- To: www-svg@w3.org
- Message-ID: <CAKjw9EYnrkJSaH7YWSezXENmAnRDkSJpGSeHavLa6Rs4DQZnmQ@mail.gmail.com>
I had prepared this around four days ago. And have been waiting a cursory check on it's reasoning. But the check went into someone's 2busy basket! I see Jonathan and Erik discussing the region. So I now post it. ----------------------------------------- I maybe unread of all svg docs. Though I cannot find a reference to zoom state detection. There is an excellent discussion on SO: <http://stackoverflow.com/questions/1713771/how-to-detect-page-zoom-level-in-all-modern-browsers> Feature request: ZoomAndPan API. In some webkit implementations zooming beyond the (implied) zoom max results in messy redraws and uncertain recentering. Currently I find islands of zoom stability with some browsers. Known (starter) use case: With a zoom level known, content visibility can be adjusted accordingly. Complication: The maximum zoom level of browsers differ. So content levels cannot be planned according to level. There is the adjacent developer interest of detecting pan state. ClarificationQ: The zoom and pan are the user actions, the scale and scroll the svg result? Being that SVG promotes scalability, this omission appears as a surprise to many newcomers. Refs: https://github.com/ariutta/svg-pan-zoom google seach <https://www.w3.org/Search/Mail/Public/search?type-index=www-svg&index-type=t&keywords=zoom&search=Search&resultsperpage=20&sortby=date&page=1> -- MarkT (+61 4) 0679 5734 ::'They promised us flying cars. Instead we got 140 characters.'
Received on Wednesday, 11 March 2015 17:00:36 UTC