I'm thinking this is normal behavior and not a bug, but if it's normal, I'd like to find a work around for my particular app. I have a tabbed layout, where the first screen is an html pro screen, loading a local html file. If loading any other plugin from there, I get a back button in the upper left corner, but if loading a screen to my other html pro page (third tap in my bottom tab bar menu, different nickname, and loads different local html file), there is no back button. Now if I go one more level deep and click an item on that second html pro page to load another screen of a different plugin type (one level deeper, or even further), a back button appears, as expected, on those screens, but only to go back as far as that 2nd html page... still no back button on the 2nd page to go to the first page (the home screen). Seems like a strange workflow to use the back button up until they get to 1 page before the home screen... then have to have the user press the first icon in the bottom tab bar instead of simply having one more back button in the same spot. Confused yet? lol This is what I'm afraid my users will fell like as well. I just don't want to get my users confused... is there a way I can add a back button to that second screen? It's almost like it's a "child view" or something, and something isn't getting pushed the way I would like it too... even if it is expected behavior. Is there something I can tweak to fix that? I tried poking around the bt_viewcontroller.m file (line 239ish), no luck. Is it because I'm going from an html pro screen to another html pro screen, so the app sees it as not another view being pushed? Thanks in advance for any light that you can shed on it for me. Working Environment: ------------------- iOS 7 Xcode 5 Self Hosted BT 3.0

Your last paragraph is spot on. Does the HTML Pro plugin have an option for Browser buttons?

It does, but places a blank white bar at the bottom of my screen, right above my tab bar. No back icon there, but even if there was, it's not in the top nav bar

Report it on http://buzz-tools.com

Not sure I completely understand your scenario, but the way I think of this navigation is as like this. The back button in the navigation bar really means 'back from this plugin', not 'back from this page'. If you are using a tab menu, you can't use back from the main item on display, because it is the 'root' for that tab. Put those two things together and certain navigation 'back' options are not always on offer. Easy enough to understand as a programmer (eventually), completely nonsensical to the end user. One way around this when you are navigating in html, i.e. calling one html page from another, is you could try dispensing with the title bar in the html pages and using html buttons to get back, maybe?

@Niraj: I've actually never seen the way that it is supposed to look when adding a browser back button. Never used one. I'm also using Chris1's tab bar utilities, and I know menu bars tend to go screwy with tabbed apps, in which a third party tab bar utility might complicate things even more (see macimage gallery, and a few others). @AlanMac: Yes, you are understanding it correctly. I had a feeling this was the case... pushing plugin pages and not screens. But how do the menu style plugins do it, while drilling down several menus deep, and allowing a back button to each previous screen? Probably by creating multiple views. So it is expected behavior, as I had guessed. As far as adding an html back button, I'm afraid that my screen real estate doesn't allow for it. I use the HTML Pro plugin, at least in this case, to create a grid style menu (it gives me a little more control and a little more flexibility than the grid menu plugin does, to control it by HTML), and the grid layout takes up up all of the screen space from top to bottom. If I allowed space for a tool bar, I'd have to adjust the size of my layout, and proportionately the width would have to be resized as well, adding more space between the items than I would like. My users will just have to deal with knowing how to properly get back to the home screen I guess :) EDIT: I have just further narrowed dow the problem. It seems that its not necessarily going from one html pro page to another... but more specifically when I go to anything in my tab bar. Climate plugin, HTML Pro plugin, facebook plugin... it's not limited. Example: 1) App loads and goes into HTML Pro page (loading local html file) 2) Going to ANY other page works fine from my html page 3) Going to ANY other page located in my tab bar provides no "back" button on the following page I know that the users should be smart enough to use the tabs instead of a back button in the upper left... but is there a way I can hard code a back button on those screens that I have in my tab bar into the nav bar, which simply goes back to my home screen? All pages in my tab bar are only 1 view deep, so no issues with sub views. Basically, I'd like to take those 4 other screens that I have links to in my tab bar, and add a button in the upper left that looks like this in pseudo code: //BACK BUTTON TAP EVENT upperLeftBackButton = 'homeScreenID'; self.view = upperLeftBackButton; (that's obviously not objective C, lol, but you get the idea of what I'm looking to do)

Switching Tabs has never resulted in a Back button availability -- it is not part of the iOS conventions. This ain't Android where the Back button records all actions to be reverse-played. :-) -- Niraj