diff options
| author | Thomas Steur <thomas.steur@googlemail.com> | 2014-09-14 16:30:18 +0400 |
|---|---|---|
| committer | Thomas Steur <thomas.steur@googlemail.com> | 2014-09-14 16:30:18 +0400 |
| commit | 69421c88b267acf3324ccb8828850e9d9390d7ae (patch) | |
| tree | 0b996f22c12614c107115d7c1081d37e7a7047e0 /misc/internal-docs | |
| parent | 37599df8123f7f2678b55c42b139d619c0a4d3b9 (diff) | |
refs #4996 some fixes, prevent JS errors on FF<9 and IE6, add random string to piwik.js to prevent caching sometimes
Diffstat (limited to 'misc/internal-docs')
| -rw-r--r-- | misc/internal-docs/content-tracking.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/misc/internal-docs/content-tracking.md b/misc/internal-docs/content-tracking.md index a9bc016d42..d2174492e2 100644 --- a/misc/internal-docs/content-tracking.md +++ b/misc/internal-docs/content-tracking.md @@ -432,8 +432,7 @@ Nothing special here I think. We would probably automatically detect the type of * Would content impressions be tracked in overlay session? * Overlay session should not trigger a content impression * Cache allowed site urls for redirects -* Test scroll event in ie9, ie10, ie11, opera -* Run JS tests in ff3, ie9, ie11, android, iphone, ms phone +* Run JS tests ms phone * Show images on hover in report * When a user clicks on an interaction, we should check whether we have already tracked the impression as the content is visible now. If not tracked before, we should track the impression as well * There can be a scroll or timer event that detects the same content became visible as well. This would not be a problem since we do not track same content block twice |