Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox m.parseProxyUrl(...) is null #2281

Closed
dweber019 opened this issue Apr 3, 2018 · 7 comments
Closed

Firefox m.parseProxyUrl(...) is null #2281

dweber019 opened this issue Apr 3, 2018 · 7 comments
Assignees
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: hammerhead TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@dweber019
Copy link

Are you requesting a feature or reporting a bug?

Bug

What is the current behavior?

Get error in firefox

✖ Should have search results for "SBB"

   1) Error on page "https://openwt.com":

      TypeError: m.parseProxyUrl(...) is null

      Browser: Firefox 59.0.0 / Mac OS X 10.13.0

         40 |
         41 |  const searchIcon = owtHomePageModel.searchIcon;
         42 |  const searchInput = owtHomePageModel.searchInput;
         43 |
         44 |  await t
       > 45 |    .click(searchIcon)
         46 |    .typeText(searchInput, 'SBB')
         47 |    .pressKey('enter');
         48 |
         49 |  const searchResultsFirstTitle = owtHomePageModel.searchResultItems.find('.title').nth(0);
         50 |

What is the expected behavior?

No error...
Btw. it runs successful in chrome, safari...

How would you reproduce the current behavior (if this is a bug)?

Run the code below ;)

Provide the test code and the tested page URL (if applicable)

Tested page URL:
process.env.HOST=https://openwt.com

Test code

import { Selector } from 'testcafe';

export default class OwtHomePageModel {
    constructor(
        public aiBanner = Selector('#block-artificialintelligencebanner').find('.title1'),
        public services = Selector('#block-services').find('.service'),
        public searchIcon = Selector('.search-container').find('.fa-search'),
        public searchInput = Selector('.search-container').find('#edit-search-block-form'),
        public searchResultItems = Selector('.search-results').find('.search-result'),
    ) { }
}

const owtHomePageModel = new OwtHomePageModel();

fixture`OWT homepage`
  .page(process.env.HOST);

test.only('Should have search results for "SBB"', async (t) => {

  const firstSearchEntry = 'Empowering the Digitalization of the Gotthard Base Tunnel with Augmented Reality';

  const searchIcon = owtHomePageModel.searchIcon;
  const searchInput = owtHomePageModel.searchInput;

  await t
    .click(searchIcon)
    .typeText(searchInput, 'SBB')
    .pressKey('enter');

  const searchResultsFirstTitle = owtHomePageModel.searchResultItems.find('.title').nth(0);

  await t
    .expect(searchResultsFirstTitle.innerText).contains(firstSearchEntry);
});

Specify your

  • operating system: OSX
  • testcafe version: 0.19.1
  • node.js version: 8.10.0
  • Firefox: 59.0.2
@LavrovArtem
Copy link
Contributor

Hi @dweber019,
I've reproduced the problem and I will investigate it.

@AlexanderMoskovkin AlexanderMoskovkin added the TYPE: bug The described behavior is considered as wrong (bug). label Apr 5, 2018
@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #11 milestone Apr 19, 2018
@LavrovArtem
Copy link
Contributor

LavrovArtem commented Apr 19, 2018

The fix is published in [email protected].

@dweber019
Copy link
Author

@LavrovArtem when will version 0.20.0 be released?

@AlexanderMoskovkin
Copy link
Contributor

@dweber019 I guess it can take one or two weeks

@SayedShahidi
Copy link

SayedShahidi commented Jun 6, 2018

Is this issue fixed because I still have the issue and i am using version 0.20.2.

@miherlosev
Copy link
Collaborator

Hi @SayedShahidi

I cannot reproduce the issue because site markup was changed and test from description now failed.
Could you please provide a simple example to reproduce?

@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: hammerhead TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

5 participants