A) Generally these are timing attacks, turning off javascript really only protects from browser-based exploitation (and they're relying on macs out of the box requiring you to do lots of clicking through boxes to be able to run binaries that weren't probed and vetted by Apple).
B) I'm actually surprised any browser is still vulnerable, in Windows and Linux at least (in addition to firmware updates and all sorts of other fixes), in browser they simply removed nanosecond-accuracy time measurement from javascript, the side channel used in most of these attacks is based on measuring the tiny time difference from something being speculatively loaded in the cache or not. No accurate clock, no side channel.