Joe, I feel your frustration. Engineering is still trying to address this.
Hi Rob,
I have tested the latest fix in build 2272, the good news is that the width/height issue is fixed for iOS device, but not for Android device. (I really don’t understand why the engineer didn’t test on Android device)
And, there is one more bug related to webView orientation I filed earlier, Case# 31803
It is a bug when playing a video in full-screen from the webView, rotate the device (don’t rotate back), click DONE to end the video (or wait for the video to finish and press DONE), the “system” width/height (such as display.contentHeight/display.contentWidth) are not updated to the current orientation even though there is an orientation event. Therefore, when exiting the video, the whole screen is messed up totally!
Could you also help to let the engineers know? They need to fix both bugs “completely” in order for webView to support orientation.
I’ll let them know. I don’t know when they can get to the other bug. You can also reply to the bug report letting them know its still broken on Android and that will keep the bug active.
Rob
I just looked at the bug report and it specifically says it was tested on Android.
I just verified that changing the webview width and
height (as in your latest test code) works find on both iPad Mini and
Galaxy Tab 3 7". This is with build 2275.
So you need to get build 2275 and try that.
Rob
It’s only a partial fix. (sign… just can’t do one step further?)
Android devices still have some problem in changing webView width/height.
It appears ok to change webView width/height but if you change more than once (using a timer delay), there is something wrong.
Or say, if a device orientation changes, changing webView width/height is still going to mess up webView. Try to rotate the device more than one time.
I have filed another bug report, Case 32270.
Does Corona has product-level manager, can I talk to him/her? It seems an endless road for webView orientation support. To report a bug, “I” test it, and find another bug. Repeat.
I am really disappointed about Corona.
I was seriously thinking to construct a tutorial site & a local learning program to promote Corona as the main development tool for mobile apps. However, with this kind of obvious bugs, passiveness & ignorance, I just have to forget about it.
Apple now presents a new language, Swift. I think I have found my solution. On the other hand, I used to think cross-platform was very important, but now I think product is much more important and once it’s approved by the market, one always has the resource to make it available for other platforms. There is no obvious reason I need to rely solely on Corona anymore.
This is a key issue with Corona Labs leadership decision making process. Priority always goes to new features that will sell more or attract more investor dollars. Bug fixes & maintenance, while going on all the time, is not the biggest priority. When you see significant issues taking months or even years (ie widgets) to resolve you know how things work around here. I learned to make peace with all this and do the best I can with the given toolset. I’m too old and too busy to learn a new trick so I’ll be around for a while longer but not out of choice really… 
WebView orientation issues still not resolved right?
This was resolved in build 2297.
Thanks for the update.
There are more issues.
I have said many times. It’s not resolved. Why ignores my previous messages.
I feel very disappointed about Corona mostly because of this webView orientation support.
I can’t believe Corona thinks it’s already resolved.
I’m just reporting what the bug tracker says. If you disagree with engineering, you are more than welcome to reply to the last message you got from the bug tracker, which will re-open the bug. Be aware they specifically mentioned that the video issue is a separate issue and needs a different bug report, but if you’re still having issues with the basic resizing after orientation, reopen the existing bug.
Rob
I have said several time Corona should treat webView support as a whole. There are many test cases and iOS/Android/Simulator all have different behaviors.
I have reported all bugs I’ve seen so far, including the full-screen video one. I am not sure if there are more bugs related because I had done so many testing during the process and I am not your QA.
Try to write a tutorial about webView orientation support, so Corona can find out all the bugs left and people will know how to do webView orientation with Corona.
Do you have the bug number for the video one?
supposed to be this one, “(Case 31803) display.contentHeight/contentWidth are not changed when video is playing in full screen”
The bug is like this,
(1) Show webView that has a video link in it
(2) Play the video (go to full screen)
(3) Rotate it (from landscape to portrait, or from portrait to landscape), BUT don’t rotate back
(4) End the video
(5) The system content.width/content.height was not changed for the rotation in step (3). This will mess up the system coordinations.
Please ask your engineer to check both actual iOS & Android devices. They behaves differently for the webView orientations. I am not sure if this is last bug related to webView orientation. Please also ask them to test “thoroughly” (rotate several times and every possible test cases), which is a basic software engineering practice.
The bug has been verified and assigned to an engineer. I’m not sure where in the queue it is to be fixed so I can’t provide an ETR.
Rob
@joe528, thanks for your efforts to get all the webView bugs reported. Had it not been for you these issues would take much longer to get resolved. Thanks for your time and energy.
I am really disappointed about Corona.
I was seriously thinking to construct a tutorial site & a local learning program to promote Corona as the main development tool for mobile apps. However, with this kind of obvious bugs, passiveness & ignorance, I just have to forget about it.
Apple now presents a new language, Swift. I think I have found my solution. On the other hand, I used to think cross-platform was very important, but now I think product is much more important and once it’s approved by the market, one always has the resource to make it available for other platforms. There is no obvious reason I need to rely solely on Corona anymore.
This is a key issue with Corona Labs leadership decision making process. Priority always goes to new features that will sell more or attract more investor dollars. Bug fixes & maintenance, while going on all the time, is not the biggest priority. When you see significant issues taking months or even years (ie widgets) to resolve you know how things work around here. I learned to make peace with all this and do the best I can with the given toolset. I’m too old and too busy to learn a new trick so I’ll be around for a while longer but not out of choice really…