Bug 25328 - [Android] WebView Renderer does not render a <div> with fixed position
Summary: [Android] WebView Renderer does not render a <div> with fixed position
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 1.2.3
Hardware: PC Mac OS
: Normal normal
Target Milestone: 1.3.4
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-12-12 08:17 UTC by Prashant Cholachagudda
Modified: 2015-05-29 12:23 UTC (History)
6 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Testcase (5.66 MB, application/zip)
2014-12-12 08:17 UTC, Prashant Cholachagudda
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Prashant Cholachagudda 2014-12-12 08:17:54 UTC
Created attachment 9048 [details]
Testcase

Xamarin.Forms v 1.2.3/v1.3 does not render correctly the elements with fixed position in a webpage.
You can reproduce this bug with Samsung Galaxy S4/S5 or Xamarin Android Player Nexus 4 (KitKat) image.

Screenshot: http://i.imgur.com/WPaxXbH.jpg & http://i.imgur.com/yXfbj5M.jpg
Comment 1 Abhishek 2014-12-18 10:00:10 UTC
I am able to reproduce this issue with AndroidFormWebView sample. On running this sample "Hello World" appears for a moment and then just blue line appears and it giving the error into the application output window.

Application Output: https://gist.github.com/Abhishekk360/b78b94582eee6d1396bd 
Screencast: http://screencast.com/t/uVQT3XcSK
Android Player Log: https://gist.github.com/Abhishekk360/77f4326e3509960e5d30

However, with AndroidNativeWebView sample I am getting "Hello World" on the screen. 

Screencast: http://screencast.com/t/fipcyYPE8nU

Build Info:

=== Xamarin Studio ===

Version 5.5.4 (build 15)
Installation UUID: 93e693b0-b53d-40f4-b29c-b61ff5cbe892
Runtime:
	Mono 3.10.0 ((detached/92c4884)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000031

=== Apple Developer Tools ===

Xcode 6.1 (6604)
Build 6A1052d

=== Xamarin.iOS ===

Version: 8.4.0.47 (Business Edition)
Hash: 7244769
Branch: 
Build date: 2014-12-11 14:54:30-0500

=== Xamarin.Android ===

Version: 4.20.0.28 (Business Edition)
Android SDK: /Users/xamarin23/Desktop/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		3.2    (API level 13)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin.Mac ===

Version: 1.10.0.18 (Business Edition)

=== Build Information ===

Release ID: 505040015
Git revision: f93940a35458a18052f1a25e106e62ca970d9c40
Build date: 2014-11-19 15:32:41-05
Xamarin addins: dc23cbd91a3a0e1d326328e1229e86c942a49ec8

=== Operating System ===

Mac OS X 10.10.0
Darwin xamarin23s-Mac-mini.local 14.0.0 Darwin Kernel Version 14.0.0
    Fri Sep 19 00:26:44 PDT 2014
    root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64
Comment 3 Jason Smith [MSFT] 2015-02-05 14:33:06 UTC
Should be resolved in 1.3.4-pre1
Comment 4 Abhishek 2015-02-10 12:14:57 UTC
I have checked this issue with "Xamarin.Forms 1.3.4.6325-pre1" and I am still observing same issue.

So I am reopening this issue.

Screencast: http://www.screencast.com/t/xzx4TB7TaEh
Application Output: https://gist.github.com/AkhileshKumar01/80e24c045f6592c3b697
Android Player Log: https://gist.github.com/AkhileshKumar01/18229d417fff651c89b0

Build Info:

Xamarin.Forms 1.3.4.6325-pre1

=== Xamarin Studio ===

Version 5.7.1 (build 17)
Installation UUID: 93e693b0-b53d-40f4-b29c-b61ff5cbe892
Runtime:
	Mono 3.12.0 ((detached/de2f33f)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 312000076

=== Apple Developer Tools ===

Xcode 6.1 (6604)
Build 6A1052d

=== Xamarin.Mac ===

Version: 1.12.0.4 (Starter Edition)

=== Xamarin.Android ===

Version: 5.0.0.17 (Trial Edition)
Android SDK: /Users/xamarin23/Desktop/android-sdk-macosx
	Supported Android versions:
		2.3    (API level 10)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin.iOS ===

Version: 8.6.1.20 (Business Edition)
Hash: 3b3ef43
Branch: 
Build date: 2015-01-24 09:42:21-0500

=== Build Information ===

Release ID: 507010017
Git revision: 0bc7d3550b6b088ac25b08dcf7bbe73bcc8658b3
Build date: 2015-02-03 19:43:29-05
Xamarin addins: f7b7d34419c9ec24501bfa7c658e80a6305613e0

=== Operating System ===

Mac OS X 10.10.0
Darwin 800BC.local 14.0.0 Darwin Kernel Version 14.0.0
    Fri Sep 19 00:26:44 PDT 2014
    root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64
Comment 5 Jason Smith [MSFT] 2015-02-11 18:33:32 UTC
This reproduction case here does not use the correct webview renderer for the
platform so it did not get hte fix. They need to set the LayoutParams of their
custom android webview to be MatchParent to get the fix.
Comment 6 Abhishek 2015-02-12 07:29:06 UTC
Thanks Jason,

If I am using Position:fixed in the AndroidNativeWebView sample “Hello World” display in the screen and If I am using Position: fixed in the AndroidFormsWebView sample  "Hello World" appears for a moment and then just blue line appears but if I change the Position:absolute then it behaving fine. 

Could you please let me know whether it is correct behavior or not?

screencast: http://www.screencast.com/t/MtAKh9de

Build Info:

Xamarin.Forms: 1.3.4.6329-pre3

=== Xamarin Studio ===

Version 5.7.1 (build 17)
Installation UUID: 93e693b0-b53d-40f4-b29c-b61ff5cbe892
Runtime:
	Mono 3.12.0 ((detached/de2f33f)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 312000076

=== Apple Developer Tools ===

Xcode 6.1 (6604)
Build 6A1052d

=== Xamarin.Mac ===

Version: 1.12.0.6 (Enterprise Edition)

=== Xamarin.Android ===

Version: 4.20.0.28 (Enterprise Edition)
Android SDK: /Users/xamarin23/Desktop/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin.iOS ===

Version: 8.6.1.24 (Enterprise Edition)
Hash: 1ee873c
Branch: 
Build date: 2015-01-31 17:42:21-0500

=== Build Information ===

Release ID: 507010017
Git revision: 0bc7d3550b6b088ac25b08dcf7bbe73bcc8658b3
Build date: 2015-02-03 19:43:29-05
Xamarin addins: f7b7d34419c9ec24501bfa7c658e80a6305613e0

=== Operating System ===

Mac OS X 10.10.0
Darwin 800BC.local 14.0.0 Darwin Kernel Version 14.0.0
    Fri Sep 19 00:26:44 PDT 2014
    root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64
Comment 7 Eric Maupin 2015-05-29 12:23:11 UTC
As Jason has stated, the sample you're testing is using a custom renderer not based on our WebViewRenderer, so it would not have received the fix.