DTM setting window.name | Community
Skip to main content
P
PaulCu3
June 14, 2017
Solved

DTM setting window.name

  • June 14, 2017
  • 2 replies
  • 787 views

Hi, we have a SPA using Angular 1.x, which we are attempting to run tests for with Protractor. We're running into some difficulty with this because it appears the DTM library is resetting the value of window.name, which is causing our Protractor tests to fail, as Angular also uses this property of the window object to store data.

Is there any way to tell DTM not to use window.name, or any other workarounds anyone can think of? Has anyone faced this problem in the past? Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by jantzen_b

Paul,

I was able to talk to one of our Adobe Consultants and they indicated they've definitely deployed DTM on Angular and not seen that issue. They did indicate it may have been a 2.x version though. Any chance you might be moving to a new version of Angular soon? If not, I'd open a ticket with Customer Care so they can get the specifics and possibly open an engineering ticket.

Thanks,
Jantzen

2 replies

jantzen_b
Adobe Employee
jantzen_bAdobe EmployeeAccepted solution
Adobe Employee
June 15, 2017

Paul,

I was able to talk to one of our Adobe Consultants and they indicated they've definitely deployed DTM on Angular and not seen that issue. They did indicate it may have been a 2.x version though. Any chance you might be moving to a new version of Angular soon? If not, I'd open a ticket with Customer Care so they can get the specifics and possibly open an engineering ticket.

Thanks,
Jantzen

P
PaulCu3Author
June 15, 2017

Thanks for your reply. Unfortunately, our application is stuck on 1.2.14 and is unlikely to be updated in the near future. We'll pursue opening a ticket with Customer Care, thanks!

Terms & ConditionsAccessibility statement

Loading footer...