Ask Questions and Find Answers

I have the same problem in 7.1.
I never find where we can change this.
I am interested if you find a solution. 

Sorry for being late on this post.

This the only way we found to get rid of that using a classic "widget page" (approved by the support, overwise we would need to use display page) : create a fragment to override the jsp which provide the anchor.

Notes : removing "" doesn't work. The anchor effect is provided by a javascript.To do that, follow the procedure detailed below. 

1) Create a new fragment module which I will call "asset-publisher-fragment" (you can create a mvc-portlet if you don't have the fragment template in you IDE, just remove every Java classes and .jsp and only keep the META-INF.ressources folder empty.

2) Edit the bnd.bnd file to add the proper "Fragment-Host" :

Bundle-Name: asset-publisher-fragment
Bundle-SymbolicName: asset.publisher.fragment
Bundle-Version: 1.0.0
Fragment-Host: com.liferay.asset.publisher.web

3) Create a new file "view_content.jsp" in  "META-INF.ressources" with the following content :

<%--
/**
* Copyright (c) 2000-present Liferay, Inc. All rights reserved.
*
* This library is free software; you can redistribute it and/or modify it under
* the terms of the GNU Lesser General Public License as published by the Free
* Software Foundation; either version 2.1 of the License, or (at your option)
* any later version.
*
* This library is distributed in the hope that it will be useful, but WITHOUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
* FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more
* details.
*/
--%>

<%@ include file="/init.jsp" %>

<liferay-util:dynamic-include key="com.liferay.asset.publisher.web#/view_content.jsp#pre" />

&lt;%
AssetPublisherViewContentDisplayContext assetPublisherViewContentDisplayContext = new AssetPublisherViewContentDisplayContext(renderRequest, assetPublisherDisplayContext.isEnablePermissions());
if (Validator.isNotNull(assetPublisherViewContentDisplayContext.getReturnToFullPageURL())) {
portletDisplay.setURLBack(assetPublisherViewContentDisplayContext.getReturnToFullPageURL());
}
%&gt;

<c:choose>
<c:when test="<%= assetPublisherViewContentDisplayContext.isAssetEntryVisible() %>">

&lt;%
AssetEntry assetEntry = assetPublisherViewContentDisplayContext.getAssetEntry();
AssetRenderer<!--?--> assetRenderer = assetPublisherViewContentDisplayContext.getAssetRenderer();
request.setAttribute("view.jsp-assetEntry", assetEntry);
request.setAttribute("view.jsp-assetRenderer", assetRenderer);
request.setAttribute("view.jsp-assetRendererFactory", assetPublisherViewContentDisplayContext.getAssetRendererFactory());
request.setAttribute("view.jsp-print", assetPublisherViewContentDisplayContext.getPrint());
request.setAttribute("view.jsp-showBackURL", assetPublisherViewContentDisplayContext.isShowBackURL());
PortalUtil.addPortletBreadcrumbEntry(request, assetRenderer.getTitle(locale), currentURL);
String summary = StringUtil.shorten(assetRenderer.getSummary(liferayPortletRequest, liferayPortletResponse), assetPublisherDisplayContext.getAbstractLength());
PortalUtil.setPageDescription(summary, request);
PortalUtil.setPageKeywords(assetHelper.getAssetKeywords(assetEntry.getClassName(), assetEntry.getClassPK()), request);
PortalUtil.setPageTitle(assetRenderer.getTitle(locale), request);
%&gt;

<liferay-util:include page="/view_asset_entry_full_content.jsp" servletContext="<%= application %>" />
</c:when>
<c:otherwise>
<liferay-util:include page="/error.jsp" servletContext="<%= application %>" />
</c:otherwise>
</c:choose>

<liferay-util:dynamic-include key="com.liferay.asset.publisher.web#/view_content.jsp#post" />

Notes : we just removed thisJS part wich annoy us :

<aui:script>
&nbsp;&nbsp;&nbsp; &nbsp;Liferay.once('allPortletsReady', function() {
&nbsp;&nbsp;&nbsp; &nbsp;if (!Liferay.Browser.isIe()) {
&nbsp;&nbsp;&nbsp; &nbsp;document
&nbsp;&nbsp;&nbsp; &nbsp;.getElementById('p_p_id_&lt;%=&nbsp;portletDisplay.getId()&nbsp;%&gt;_')
&nbsp;&nbsp;&nbsp; &nbsp;.scrollIntoView();
&nbsp;&nbsp;&nbsp; &nbsp;}
&nbsp;&nbsp;&nbsp; &nbsp;});
&nbsp;</aui:script>

4) Deploy the module and, that's it. 

Hi Henry, we solved the same way long ago. Thank you anyway!

Here is my awful solution for this awful behaviour.

Liferay.Browser.isIe = () => true;

This script has to be called as late as possible and this to avoid other Liferay scripts to consider your browser as IE. As the "allPortletsReady" event is fired after the DOM is rendered, this should'nt be a problem. 

Hope this helps.

J.