blackberry / bbUI.js

BlackBerry UI look and feel JavaScript toolkit for WebWorks
Apache License 2.0
313 stars 194 forks source link

BB10 Screens not going back or forward #320

Closed Bjern closed 11 years ago

Bjern commented 11 years ago

I know this is similar to my previous issue which I said was resolved, but we're now talking about a different device.

The previous issue was about the scenario where a user goes from screen 1 -> 2 -> 3 and then tries to get back. After going back 3 -> 2 -> 1 and clicking on a menu; screen 1 would stack screen 2 below it. THIS IS RESOLVED on my curve phone.

However it worked fine on BB10 before I updated. I am now using bbui 0.9.4 (yes I know its beta) and it seems to be worse. Why? I can go 1 -> 2 -> 3 then back 1 screen ONLY. ie: 1 -> 2 -> 3-> 2 then it stops working. Can't go forward or back, nothing. Similarly I can go 1 -> 2 -> 1 then nothing. Can always click back only once.

Is anyone else having this trouble on dev alpha with bbui? Is there another issue being worked on I'm not aware of? BTW I get no errors in the web inspector. The only thing there is the info / warning message: event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future. WHICH increments every time I click on an image list.

I can supply project code, its a free app only valuable to a small niche of people. BTW how do I label this BB10 and Playbook?

tneil commented 11 years ago

Very odd.. I tested this on BB10 and on BB6/7 and it was working for me. I'll test again when I get into the office


Sent from my Awesome BlackBerry Smartphone

From: Bjern [mailto:notifications@github.com] Sent: Sunday, September 02, 2012 08:19 AM To: blackberry/bbUI.js bbUI.js@noreply.github.com Subject: [bbUI.js] BB10 Screens not going back or forward (#320)

I know this is similar to my previous issue which I said was resolved, but we're now talking about a different device.

The previous issue was about the scenario where a user goes from screen 1 -> 2 -> 3 and then tries to get back. After going back 3 -> 2 -> 1 and clicking on a menu; screen 1 would stack screen 2 below it. THIS IS RESOLVED on my curve phone.

However it worked fine on BB10 before I updated. I am now using bbui 0.9.4 (yes I know its beta) and it seems to be worse. Why? I can go 1 -> 2 -> 3 then back 1 screen ONLY. ie: 1 -> 2 -> 3-> 2 then it stops working. Can't go forward or back, nothing. Similarly I can go 1 -> 2 -> 1 then nothing. Can always click back only once.

Is anyone else having this trouble on dev alpha with bbui? Is there another issue being worked on I'm not aware of? BTW I get no errors in the web inspector. The only thing there is the info / warning message: event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future. WHICH increments every time I click on an image list.

I can supply project code, its a free app only valuable to a small niche of people.

— Reply to this email directly or view it on GitHubhttps://github.com/blackberry/bbUI.js/issues/320.


This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

tneil commented 11 years ago

Wierd... I just tried this on BB10 version 10.0.6 and I can do the following without any issues

Bjern commented 11 years ago

Ok, so by process of elimination... I had it working on BB10. I then added code to make it work nicely on Curve. The BB10 automatically inserts the back button into the title whilst Curve needs the extra code.

Save
Cancel

insert app code here then at the bottom of the page ...

Could this duplicate back and save action code cause the stopping of page transition? Something is stopping my app from moving after the first time back is clicked on any of these buttons, and its NOT reporting any errors to the inspector. Suggestions?

tneil commented 11 years ago

Why did you need to insert code on the curve for the back button.. bbUI uses the hardware back button on BB5/6/7 phones to handle going "back"

Bjern commented 11 years ago

Well exactly! On the samples the back button works but on my app it didn't and I couldn't figure out why. I also found that on BB10 the back button shows in the title BUT doesn't SHOW anywhere on the curve. Users are not sure that they can even go back because there was no back button. In fact there were NO buttons. I had to add the menu to get some kind of functionality.

On BB10 the title tag supplied above works great for back and save. It does nothing on curve except provide a black title border across the top. Which I understand is inline with the Curve ui.

I tried:

  1. Using the action bar on its own but it has no effect on curve.
  2. Using the title bar with a back option - no effect on curve.
  3. Using the menu div - curve now has a back option.

Basically I developed for BB10... found that curve would not work smoothly, switched to making it right for curve then came back to BB10 and now BB10 no longer works properly. Is there a way I can supply you the entire app, you may take one look at the code and find my problem, I could just be using bbui the wrong way?

Bjern commented 11 years ago

BTW should I remove the id's from my pushScreens? I see some chatter around that causing trouble with the transitioning. ALL my screens I push have been assigned ID's

UPDATE: I removed the id's and this had no change, it also prevented the image list in the app from working on Playbook. So no id's left curve working fine, BB10 still not working properly when I click back, and caused Playbook to stop working - menus don't go anywhere

tneil commented 11 years ago

Correct, there is no back button in the UI on BB5/6/7 this is by design.

On an older BlackBerry you must press the hardware back button like in other applications. You must make sure you have the proper features defined in your config.xml file in order for it to work. These are outlined in the docs and in the sample config.xml

Are you saying that with the proper features in the config.xml the hardware back button is not moving the screens back on a curve?

I have tested this on BB5/6/7 on multiple devices and it is working, as well with many other developers.

If this is the case, you may have an exception in your JavaScript somewhere causing an issue and haulting the code


Sent from my Awesome BlackBerry Smartphone

From: Bjern [mailto:notifications@github.com] Sent: Wednesday, September 05, 2012 07:08 AM To: blackberry/bbUI.js bbUI.js@noreply.github.com Cc: Tim Neil Subject: Re: [bbUI.js] BB10 Screens not going back or forward (#320)

Well exactly! On the samples the back button works but on my app it didn't and I couldn't figure out why. I also found that on BB10 the back button shows in the title BUT doesn't SHOW anywhere on the curve. Users are not sure that they can even go back because there was no back button. In fact there were NO buttons. I had to add the menu to get some kind of functionality.

On BB10 the title tag supplied above works great for back and save. It does nothing on curve except provide a black title border across the top. Which I understand is inline with the Curve ui.

I tried:

  1. Using the action bar on its own but it has no effect on curve.
  2. Using the title bar with a back option - no effect on curve.
  3. Using the menu div - curve now has a back option.

Basically I developed for BB10... found that curve would not work smoothly, switched to making it right for curve then came back to BB10 and now BB10 no longer works properly. Is there a way I can supply you the entire app, you may take one look at the code and find my problem, I could just be using bbui the wrong way?

— Reply to this email directly or view it on GitHubhttps://github.com/blackberry/bbUI.js/issues/320#issuecomment-8294570.


This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

tneil commented 11 years ago

All screens require an id, the issue around non unique ids was solved in the next branch


Sent from my Awesome BlackBerry Smartphone

From: Bjern [mailto:notifications@github.com] Sent: Wednesday, September 05, 2012 07:34 AM To: blackberry/bbUI.js bbUI.js@noreply.github.com Cc: Tim Neil Subject: Re: [bbUI.js] BB10 Screens not going back or forward (#320)

BTW should I remove the id's from my pushScreens? I see some chatter around that causing trouble with the transitioning. ALL my screens I push have been assigned ID's

— Reply to this email directly or view it on GitHubhttps://github.com/blackberry/bbUI.js/issues/320#issuecomment-8295126.


This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Bjern commented 11 years ago

I have managed to resolve this. Although there were no errors reported I found that an included javascript file was the cause. I have removed the code and all is well. Not a bug.

tneil commented 11 years ago

Cool.. glad to hear your problem is solved.. and thanks for following up on this issue