Mention backBehavior: fullHistory on web docs

Author: satya164

versioned_docs/version-7.x/web-support.md

@@ -21,7 +21,14 @@ While Web support works out of the box, there are some things to configure to en
 
    You may be familiar with using `navigation.navigate` to navigate between screens. But it's important to avoid using it when supporting the web. Instead, use the `Link` or [`Button`](elements.md#button) components to navigate between screens. This ensures that an anchor tag is rendered which provides the expected behavior on the web.
 
-3. [**Server rendering**](server-rendering.md)
+3. [**Adapt to web-specific behavior**](web-specific-behavior.md)
+
+   Depending on your app's requirements and design, you may also want to tweak some of the navigators' behavior on the web. For example:
+
+   - Change `backBehavior` to `fullHistory` for [tabs](bottom-tab-navigator.md#backbehavior) and [drawer](drawer-navigator.md#backbehavior) on the web to always push a new entry to the browser history.
+   - Use sidebars on larger screens instead of [bottom tabs](bottom-tab-navigator.md#tabbarposition) - while not specific to web, responsive design much more important on the web.
+
+4. [**Server rendering**](server-rendering.md)
 
    Currently, React Navigation works best with fully client-side rendered apps. However, minimal server-side rendering support is available. So you can optionally choose to server render your app.