3 ms·
one more reason to use flash-block. maybe chrome should play flash only after confirmation by default.
by growt 15y ago
one more reason to use flash-block.
maybe chrome should play flash only after confirmation by default.
- tjoff 15y agoI haven't seen a flash-block implementation in chrome that hinders execution of flash. Often the flash is able to load before it is blocked which kind of defeats the purpose (from a security standpoint). Or have I missed something?
- daeken 15y agoIf you enable click-to-play for plugins, it'll prevent it from loading whatsoever before you click it.
- tjoff 15y agoCan't believe I didn't know about that. But I can't find it? (all I can find is that is supposed to be in about:flags) Is it available in stable chrome releases? Edit: Never find what I'm looking for in chrome settings... It's in Options -> Under the hood -> Content settings... (or just chrome://settings/content ) and then you can enable click-to-play under plugins. Thanks!