How to retrieve the results from js and how store those values in sobject? #50
Commits on Aug 7, 2015
Commits on Aug 10, 2015
Commits on Aug 17, 2015
Commits on Aug 20, 2015
-
Merge pull request #21 from bluesmoon/quoted-cookies
Quoted cookies
Commits on Aug 24, 2015
Commits on Sep 8, 2015
Commits on Feb 29, 2016
-
Merge pull request #68 from lognormal/soasta-2015
SOASTA 2015 Contributions
Commits on Mar 17, 2016
Commits on Mar 21, 2016
Commits on Mar 22, 2016
Commits on May 9, 2016
Commits on May 15, 2016
Commits on May 18, 2016
-
error thrown as 'this.session' is undefined, when site_domain is provided as an option from config. looking at the code this.session.domain is not used anywhere, so removing its ref.
-
Merge pull request #87 from luckykurhe/bugfix_session_site_domain
this.session not defined
Commits on Jun 10, 2016
Commits on Jun 24, 2016
-
-
-
-
09-backbone/00-simple.html now uses the boomerang snippet instead of …
…the direct embedded include
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Bug 101437: Check location.href before performance to avoid Chrome cr…
…ash on X-O frames
-
-
-
-
-
-
-
Merge pull request #332 from SOASTA/bug-dependencies
Adds the required mocha dependency for grunt tests
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Add banner and build flags to add banner to code
* Add banner and build flags to add banner to code * Add MD5 copyright
-
-
-
-
-
-
-
* Initial third party analytics plugin * Capture third party analytics campaign information * Move getQueryParamValue to BOOMR.utils
-
Fix bug with duplicate XHR URLs returning incorrect timing
* Fix bug with duplicate xhr urls returning incorrect timing * Add sanity check when using data from resource timing * Create XHR urls dynamically
-
Documentation using JSDoc and Markdown + AutoXHR docs
* Add JSDoc support and build target to Gruntfile.js * Add JSDoc style documentation and migrate existing HTML documentation to markdown * Use SOASTA fork of jsdoc with disabled strict mode
-
-
-
Add support for IBM Site Promotion Analysis and Real Estate Analysis
* Add support for IBM Site Promotion Analysis and Real Estate Analysis * Add hasOwnProperty check
Commits on Jun 26, 2016
-
-
-
-
-
-
-
-
-
-
Build boomerang-latest-debug.js with a custom plugin that runs BOOMR.…
…init() when it's loaded
-
-
-
If Boomerang isn't ready to send a beacon when BOOMR.responseEnd is c…
…alled, add it to the beacon as "qt"
-
Commits on Jun 27, 2016
-
-
Merge pull request #92 from ryanhughes/package-install
Fix npm error running webdriver-manager when it's not installed
Commits on Jun 29, 2016
Commits on Oct 18, 2016
-
Add missing Mocha dev dependency (#107)
Mocha is used as the test runner via `karma-mocha`. `karma-mocha` relies on the availability of mocha as a peer dependency, but boomerang does not define mocha a dev dependency.
Commits on Oct 19, 2016
-
Merge pull request #98 from SOASTA/soasta-2016-q2
SOASTA 2016 Q2 Contributions
Commits on Nov 25, 2016
-
-
Merge pull request #115 from bripkens/update-readme-docs
Update README to account for changed build procedure
Commits on Dec 1, 2016
-
Wraps removeEventListener to work with the wrapped functions we use f…
…or addEventListener calls
-
-
Commits on Jan 13, 2017
Commits on May 2, 2017
-
-
Make the errors plugin work without the Compression plugin (#138)
Without the compression plugin, you can't directly try to access Compression.jsUrl and must first check for Compression itself. And getErrorsForUrl should return the serialized errors.
-
Commits on May 13, 2017
Commits on May 16, 2017
Commits on Oct 30, 2017
Commits on Nov 20, 2017
Commits on Nov 29, 2017
-
Compare marks/measures to performance.now mark (#158)
When using the User Timing API plugin, only the first beacon sent will include User Timing API data. Susbsequent beacons will not collect newly set User Timing API data due to comparing incorrect timestamps. To reproduce: 1. Add code to a test page running Boomerang. Something like the following would suffice: ``` performance.mark('pre-load-mark'); addEventListener('load', () => { setTimeout(() => { console.log('marking'); performance.mark('post-load-mark'); }, 5000); }); ``` 2. Load the page with Boomerang, the User Timing API plugin and the sample code 3. After the `load` event fires, inspect the Network tab to see that a beacon was sent with the User Timing API data, including the 'pre-load-mark' mark. The 'post-load-mark' should not be present. 4. Fire another beacon from the console with: `BOOMR.requestStart('test').loaded();` 5. Notice that the expected 'post-load-mark' is not present in the beacon. On line [41 in plugins/usertiming.js](https://github.com/SOASTA/boomerang/blob/master/plugins/usertiming.js#L41), the `from` value is set to `BOOMR.now()`. This value is a millisecond timestamp derived from `Date.now()`. When subsequent beacons are fired, the mark/measure's `startTime + `duration` is [compared](https://github.com/nicjansma/usertiming-compression.js/blob/master/src/usertiming-compression.js#L388) to the `from` timestamp. Since the mark/measure is using `performance.now()` instead of `Date.now()` to set the time, the value will always be less than the `Date.now()` timestamp. Thus, the data is considered old and is removed from the compressed data. The fix for the issue is to use `performance.now()` instead of `Date.now()` when setting the `from` value. Since this function isn't called unless the User Timing API is available, it should be safe to directly call `performance.now()` without any defensive coding.
Commits on Dec 6, 2017
-
Add support for Network Information API (#160)
* Add support for Network Information API The Network API is a revision of the `navigator.connection` interface that attempts to provide a standard, cross-browser interface to access information about network conditions. This commit updates the mobile plugin to source network information from the newer source where available. This plugin works by first trying to find connection information from various places depending on the browser. It then tries to map data from the identified interface to variables that have historically been used by Boomerang. Effectively, this commit simply makes Boomerang aware of the new locations of information from the Network Information API. Credit for this work goes to @bluesmoon, with assistance from @tollmanz to verify and write tests. * Rewrite mobile.js as a Boomerang plugin The mobile.js plugin was not previously written as a plugin. This commit updates the code to make it a plugin and implement the same interface as other plugins. This allows for disabling the plugin as needed and initializing the plugin in a consistent manner. This commit also adds the `saveData` value from the Network Information API if it is available. * Use bind to set correct this * Remove bind for cross-browser compat * Validate type of variable before adding to beacon