[wearable] Bizarre difference between 2.3.2 and 3.0 web view

에 의해 GO U

2017년 08월 25일 13:05 영어 (English) 6 댓글

Hi, I found some strange behavior of web view for 3.0 wearable.

At first, please look below screenshot:

I tried to show simple HTML page on web view, and expected that 2.3.2 and 3.0 web view show completely same screen. But as you can see, 3.0 shows smaller size of images than 2.3.2.

They display different sizes of images, even if they are fixed as 100 pixels. I don't think that it happens due to resolution difference between 2.3.2 and 3.0, because they share same screen resolution(360*360). And output of 2.3.2 seems to be right because 100px is not so small for 360*360 resolution :)

Can someone explain the reason of this for me? Do you guys think it happens only in the emulator, not real device?

I have to prepare for app update for Gear S4, the first Tizen 3.0 device, but it bothering me :(

Edited by: GO U on 25 8월, 2017

Responses

6 댓글

Yasin Ali

2017년 08월 28일 22:22

Hi,

Could you please share some of your code to test. You nay check again your project code html aligning etc.

On version change webview may behave behave differently as you said. For project purpose you should adapt

that behavior meeting project requirements.

Check out below helpful links also:

1. https://developer.tizen.org/development/guides/native-application/connectivity-and-wireless/internet-and-contents-downloads/web-view

2. https://developer.tizen.org/development/api-references/native-application?redirect=/dev-guide/3.0.0/org.tizen.native.wearable.apireference/group__WEBVIEW.html

3. https://developer.tizen.org/community/tip-tech/webview-native-application-browsing-multiple-tabs

Hope it will help.

이 게시물에 답글 달기
답변으로 선정

GO U Yasin Ali

2017년 08월 28일 23:50

Thank you very much for your replay. Tested HTML code is very simple.

<img src='star.png' width=100/>

It is all. It shows diffrent size of image on 2.3.2 and 3.0 wearable emulator. In my guess, result on 3.0 seems to be wrong because it looks like under 100px obviously.

And I tried it again with webview example code from the link what you provided, but result was same.