fallback to offset calculation if it does not exist

had trouble testing locally, but this should at the very least not change any behavior if the current browser has a defined offsetX/offsetY property.