Comment 2 for bug 1537248

The haptic feedback including the DBus API used to lookup the setting is not version-specific, the code lives in src/Ubuntu/Components/1.1/Haptics.qml and is used even with 1.3 via ucabstractbutton.cpp and uchaptics.cpp. The default is true, meaning if the setting doesn't work it will indeed always vibrate.

After adding "onErrorChanged: console.log(error)" to the vibra object (at the very bottom) in Haptics.qml I got the following running Calculator:
qml: An AppArmor policy prevents this sender [...] interface="org.freedesktop.Accounts" member="FindUserById" [...]

So by the looks of it Calculator can't read the setting.