Not really. I'm just trying to use the wheel; it's other people that have implemented it wrong.
Found a bodge. Basically create a DIV at 0,0 and then call its getClientBoundingRect() and measure the distance. Then the error cancels itself out. Phew.
- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
- You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
- You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
- If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "HTML: Translating touch events to relative"
Collapse
-
I suspect you are trying to reinvent the wheel.
Try looking at a library:
Hammer.JS - Hammer.js
QuoJS
Daniel Glyde: TouchIt: jQuery Plugin for Touch events
Leave a comment:
-
HTML: Translating touch events to relative
This is one of those "I can't believe it's this hard" problems.
I need to translate a mouse press or touch on a web page to a div's local coordinates. Any sensible system would do this for you, but that's too simple for the folks behind the HTML standards. After a lot of faffing, I've come up with this (ignoring x for brevity):
If I have a DIV that starts 300 pixels down the page and I touch its top left, e.y = 300 and r.top is 300, and so it works. If the window is scrolled down so my div is at the top of the window then r.top is now 0 because it's offset by the scroll position (bizarrely - I don't know why anybody would think that's how it should be) which is why you also need to subtract the scroll position.Code:function onTouchStart( ev ) { e = new Object; e.y = ev.touches[0].pageY; // translate r = rootDiv.getBoundingClientRect(); e.y -= r.top; e.y -= window.scrollY; }
This is fine. Until I zoom in on Android (Chrome).
Once zoomed if I scroll so my div is at the top r now doesn't take into account the scroll position, so that r.top is 300 and scrollY is 300 and I therefore end up 300 pixels out.
So how the ***** am I meant to make that work? Is there some alternate strategy?
Any insights?Tags: None
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers
Contractor Services
CUK News
- Should a new limited company not making much money pay a salary/dividend? Today 08:43
- Blocking the 2025 Loan Charge settlement opportunity from being a genuine opportunity is… HMRC Yesterday 07:41
- How a buyer’s market in UK property for 2026 is contractors’ double-edge sword Feb 11 07:12
- Why PAYE overcharging by HMRC is every contractor’s problem Feb 10 06:26
- Government unveils ‘Umbrella Company Regulations consultation’ Feb 9 05:55
- JSL rules ‘are HMRC’s way to make contractor umbrella company clients give a sh*t where their money goes’ Feb 8 07:42
- Contractors warned over HMRC charging £3.5 billion too much Feb 6 03:18
- Statutory Sick Pay (SSP) for umbrella company contractors: an April 2026 explainer Feb 5 07:19
- IR35: IT contractors ‘most concerned about off-payroll working rules’ Feb 4 07:11
- Labour’s near-silence on its employment status shakeup is telling, and disappointing Feb 3 07:47

Leave a comment: