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
LPS-143919 Simulation iframe allows the user to interact with the control menu #6887
Conversation
To conserve resources, the PR Tester does not automatically run for every pull. If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed. If your pull was never tested, comment "ci:test" to run the PR Tester for this pull. |
ci:test:sf |
✔️ ci:test:sf - 1 out of 1 jobs passed in 4 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-143919 1 Successful Jobs:For more details click here. |
ci:test:relevant |
Jenkins Build:test-portal-source-format#4487 Jenkins Report:jenkins-report.html Jenkins Suite:sf Pull Request:liferay-echo#6887 Testray Routine:EE Pull Request Testray Importer:publish-testray-report#1682 |
✔️ ci:test:stable - 11 out of 11 jobs passed✔️ ci:test:relevant - 26 out of 27 jobs passed in 1 hour 27 minutesClick here for more details.Base Branch:Branch Name: master Upstream Comparison:Branch GIT ID: 410d9593cb9ec56cba8dca1d2035405257627714 ci:test:stable - 11 out of 11 jobs PASSED11 Successful Jobs:
ci:test:relevant - 25 out of 27 jobs PASSED2 Failed Jobs:25 Successful Jobs:
For more details click here.This pull contains no unique failures.Failures in common with acceptance upstream results at 410d959:
|
Jenkins Build:test-portal-acceptance-pullrequest(master)#1930 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-echo#6887 Testray Routine:EE Pull Request Testray Build:[master] ci:test:relevant - beltranrengifo > liferay-echo - PR#6887 - 2022-01-09[23:28:25] Testray Importer:publish-testray-report#6005 |
ci:test:echo |
❌ ci:test:echo - 15 out of 22 jobs passed in 2 hours 44 minutesClick here for more details.Base Branch:Branch Name: master Upstream Comparison:Branch GIT ID: b348076325e5c8ae22676237c2cbbd0299156056 ci:test:echo - 15 out of 22 jobs PASSED7 Failed Jobs:
15 Successful Jobs:
For more details click here.Failures unique to this pull:
Failures in common with acceptance upstream results at b348076:
|
Jenkins Build:test-portal-acceptance-pullrequest(master)#1485 Jenkins Report:jenkins-report.html Jenkins Suite:echo Pull Request:liferay-echo#6887 Testray Routine:EE Pull Request Testray Build:[master] ci:test:echo - beltranrengifo > liferay-echo - PR#6887 - 2022-01-10[03:27:28] Testray Importer:publish-testray-report#4406 |
d5f76cf
to
28afdbc
Compare
ci:test:sf |
✔️ ci:test:sf - 1 out of 1 jobs passed in 3 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-143919 1 Successful Jobs:For more details click here. |
ci:forward |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
Skipping previously passed test suites: |
Jenkins Build:test-portal-source-format#5603 Jenkins Report:jenkins-report.html Jenkins Suite:sf Pull Request:liferay-echo#6887 Testray Routine:EE Pull Request Testray Importer:publish-testray-report#1905 |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#111918 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#1490 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-echo#6887 Testray Routine:EE Pull Request Testray Build:[master] ci:test:relevant - beltranrengifo > liferay-echo - PR#6887 - 2022-01-10[08:01:48] Testray Importer:publish-testray-report#4417 |
See Jira issue
Original PR
Motivation
Get rid of a weird app-in-app situation on the simulator device panel, due to the presence of the control menu after the first navigation.
The param
p_l_mode=preview
used for hiding this menu only works for the first load of the iframe.Solution proposed
Now, the JS verifies if the param is present after a navigation, adding it if needed.
In case portal navigation occurs, a listener will handle the DOM to create a smooth transition between pages vía CSS.
Steps
Actual: The new loaded page shows the control menu
Expected: The new loaded page does not display the control menu
Note: after navigation, a visible delay before hiding the control menu is expected