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

Fix Flyout placement for versions <RS5 #2676

Merged
merged 266 commits into from
Jun 26, 2019
Merged

Fix Flyout placement for versions <RS5 #2676

merged 266 commits into from
Jun 26, 2019

Conversation

khetanashita
Copy link
Contributor

@khetanashita khetanashita commented Jun 25, 2019

Some options for flyout placement were added in RS5 (like FlyoutPlacementMode::BottomEdgeAlignedLeft, TopEdgeAlignedLeft and LeftEdgeAlignedTop).

Adding a check to avoid failure for <RS5 devices.

Microsoft Reviewers: Open in CodeFlow

Office VSTS Default Agent and others added 30 commits June 11, 2019 18:22
* Fix first launch and reload/unload issue

* Reword the error message

* rename the helper to wrapper

* PrepareJavaScriptRuntime from 750ms to 5s

* use shared_from_this

* remove ThisWrapper

* ReactControl in rt to shared_ptr
A few deprecations and refactorings caused issues with the upgrade to 0.58. This was all the changes to JS necessary to get RNTester working.
* Refactored root folders
* Updated path references
* Fixed appveyor.yml
* Update CODEOWNERS
* Remove old ISSUE_TEMPLATES
* Committing changes to master readme

* Updating to address review feedback
* Define test WebSocket types.

* Use CRLF for C++ files.

* Try basic_stream_socket over IWebSocketStream.

* Use boost::beast::test::stream.

* Defined async_connect(test::stream& ...

* Move custom async_connect into WebSocket.cpp.

* Defined MockStreamLayer subtype.

* Use errc::make_error_code.

* Define MockStream, equivalent to websocket::stream

* Implement async read and write in MockStreamLayer.

* Override boost::beast::http::async_read and write.

* Move TestWebSocket implementation to CPP file.

* Stop including <boost/beast/experimental/test/stream.hpp>.

* Simplify template decls for SecureWebSocket.

* Simplified WebSocket template declaration.

* Updated namespace for WebSocket-related APIs.

* Reset default platform to x64 in SLN.

* Re-located BaseWebSocketTest.
* End of line updates for inconsistent CPP files.

* Fixed symbol typo.
* Committing a new readme file for "current" and making updates to main readme, vnext readme and other files to reflect the same

* Updated releases link
* Minor updates to readme

* Update README.md

* Update README.md
* Adding manual install steps and steps for running sample apps through cloning repo.

* Updated sdk version

* Update vnext/docs/GettingStarted.md

Co-Authored-By: harinikmsft <[email protected]>

* Update vnext/docs/GettingStarted.md

Co-Authored-By: harinikmsft <[email protected]>
acoates-ms and others added 15 commits June 11, 2019 18:22
* draft

* workaround cppwinrt error

* popup fix

* rollback change to popup and update Flyout

* update comment from popup to flyout

* change signature and rename getShadowNodeWithXamlRoot

* draft

* workaround cppwinrt error

* popup fix

* rollback change to popup and update Flyout

* update comment from popup to flyout

* change signature and rename getShadowNodeWithXamlRoot

* install SDK

* install SDK for win32

* install desktopcpp
* Add accessibilityLiveRegion property to FrameworkElementViewManager
* Added AccessibilityUtils.h with helper method to announce the LiveRegion change
* Fixed bug and added example in RNTester
@khetanashita khetanashita requested a review from a team as a code owner June 25, 2019 16:54
@ghost ghost added the vnext label Jun 25, 2019
@chrisglein
Copy link
Member

What's going on with the commit history of this PR? (264 commits)

@ahimberg
Copy link
Member

What's going on with the commit history of this PR? (264 commits)

This seems to happen with people that submit a pull request from their fork/master instead of making a branch in their repo. But yeah because of 264 commits you can't use codeflow to review the changes

@chrisglein
Copy link
Member

What's going on with the commit history of this PR? (264 commits)

This seems to happen with people that submit a pull request from their fork/master instead of making a branch in their repo. But yeah because of 264 commits you can't use codeflow to review the changes

Ah, that explains it. Good candidate for something to add to a contribution guide (it's mentioned in react-native's here, CoreCLR's here, and WinUI's here

@khetanashita
Copy link
Contributor Author

What's going on with the commit history of this PR? (264 commits)
This seems to happen with people that submit a pull request from their fork/master instead of making a branch in their repo. But yeah because of 264 commits you can't use codeflow to review the changes

Ah, that explains it. Good candidate for something to add to a contribution guide (it's mentioned in react-native's here, CoreCLR's here, and WinUI's here

My bad. I'll make sure to work off of a dedicated branch rather than master.

vnext/ReactUWP/Views/FlyoutViewManager.cpp Outdated Show resolved Hide resolved
@khetanashita khetanashita merged commit 43db5b7 into microsoft:master Jun 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.