Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/matomo-org/matomo.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/misc
diff options
context:
space:
mode:
authorThomas Steur <thomas.steur@googlemail.com>2014-09-13 17:21:46 +0400
committerThomas Steur <thomas.steur@googlemail.com>2014-09-13 17:21:46 +0400
commit0f12cc9a8725636c04fdfc42bc576f337b8ec2f8 (patch)
tree560a9de9c5d01888ae26e04b7713aaafb7a4c841 /misc
parent92e2aa09d8c787d463b38fb404fd0da75dddc0b6 (diff)
refs #4996 allow redirects to subdomains of known hosts
Diffstat (limited to 'misc')
-rw-r--r--misc/internal-docs/content-tracking.md7
1 files changed, 2 insertions, 5 deletions
diff --git a/misc/internal-docs/content-tracking.md b/misc/internal-docs/content-tracking.md
index 58b16fa5f3..0f7c8aa5f9 100644
--- a/misc/internal-docs/content-tracking.md
+++ b/misc/internal-docs/content-tracking.md
@@ -429,15 +429,12 @@ Yes it seems most logical to create an action entry for each Content.
Nothing special here I think. We would probably automatically detect the type of content (image, video, text, sound, ...) depending on the content eg in case it ends with [.jpg, .png, .gif] it could be recognized as image content and show a banner in the report.
## TODO
-* Redirect to URL in piwik.php only if a known site (site table in Piwik)
* Would content impressions be tracked in overlay session?
* Overlay session should not trigger a content impression
* Test scroll event in ie9, ie10, ie11, opera
-* Run JS tests in ff3, ie7, ie8, ie9, ie10, ie11, opera, android, iphone, ms phone, safari
-* Write PHP tests
+* Run JS tests in ff3, ie7, ie8, ie9, ie11, android, iphone, ms phone
+* Write UI test
* Show images on hover in report
-* Better position #contenttest in JS tests to make isNodeVisible work on all platforms
-* makeNodesUnique should return same result on all browsers. It does currently but different order which is no problem at all but makes test work in all browsers
* 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
* Maybe v2