Have Report Site Issue detect the Marfeel JS library
Categories
(Web Compatibility :: Tooling & Investigations, enhancement, P1)
Tracking
(Not tracked)
People
(Reporter: karlcow, Assigned: ksenia)
References
Details
The goal is to make the Reporter detects automatically when Marfeel is used on a Website.
See Bug 1149160 for the context about Marfeel.
This is done in the context of Web Compatibility 2019Q2 work
https://github.com/mozilla/webcompat-team-okrs/issues/79
This will require to discover the pattern for marfeel library
On the server side, it will be handled by https://github.com/webcompat/webcompat.com/issues/2844
(see previously Bug 1535479 for FastClick)
![]() |
Reporter | |
Comment 1•6 years ago
|
||
A first strategy would be to detect a request to
https://bc.marfeel.com/statics/marfeel/gardac.js
There is also a window.marfeel object being created.
That would be very similar to the FastClick issue, and we could probably reuse most of the code.
{
"title": "reporter libraries detector",
"last_update": "2019-04-15",
"libraries": [
{
"name": "marfeel",
"window": "window.marfeel",
"bugzilla": 1544358,
"label": "type-marfeel"
},
{
"name": "fastclick",
"window": "window.FastClick",
"bugzilla": 1149160},
"label": "type-fastclick"
}
]
}
![]() |
Reporter | |
Comment 2•6 years ago
|
||
I surveyed websites in the see also of Bug 1149160.
All the sites with marfeel had the window.marfeel object.
Comment 4•6 years ago
|
||
Similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1544359, feel free to fix both bugs in a single patchset.
Comment 5•6 years ago
|
||
This was recently fixed in bug 1544359.
Updated•6 years ago
|
Description
•