Web BrowserNX

When editting a field on the page (WebBrowserNX text input field), the pop-up keyboard has a "Go" button on it.

I can't find documenation specifically on its behavior, but from doing some testing, I believe the behavior is:
1 - If the user is editting the only visible field on the page, it will close the pop-up keyboard and cause a submit action on the containing form (not cause any button clicks, just the submit action).

2 - Editting other fields, it will just close the pop-up keyboard.

Can you confirm that this is the behavior to expect across all devices? (I only have one device sample size and have just tested by tweaking some of my pages, since it was a little different across my pages).

If there is doc related to that, feel free to point me to it, but I wasn't able to find any.

Our application doesn't support being navigated away from and back to.

So, I disable the back button as early in the loading of the page as possible (just an in-line javascript call, before a pageLoad or anything else).
I attempt to disable the menu button as well (which is supported on some devices, but not all, from what I see) and otherwise minimize the menu list.
On the devices, that only allow minimizing the menu list, 2 of the 3 remaining options (About & navigate to Initial), both navigate away from our application. At which point, returning to our application, puts us in a bad state.

I'm adding a warning message that will display if an attempt is made to navigate away from our page (for the devices that can't have the menu hidden and the user picks About/InitialPage).
I've made some unsuccessful attempts to detect if our page is being returned to, so I could at least log the user out of our system, so they can return to a valid state (the javascript won't re-execute, pageload isn't called again.. read some things about pagestate which didn't seem to fire on the return as well as that at one point hooking onpageunload would prevent the cached instance from being used...then ran out of ideas).

Somewhere internally, the Ricoh system knows that the page has been returned to, because when I disable the back button during page initialization, that value is unset whenver the next page is loaded... when the user navigates 'back' to that page... even though none of my code is executed again, the back button is enabled again... so it is treating it like a reload.

1 - Is there a way to detect if the page is navigated back to?

2 - I know our C306Z doesn't allow disabling of the menu button. What percentage of models, don't allow that? (I assume either that was just a problem with early devices, and anything new will... or, that was a requested feature that was added to the API to prepare for when it will be available, and that nothing does yet).

3 - Do you have any suggestions that i've not considered or where I've missed something?

Thanks,

Scott

I have a few issues and questions to go through.

1 - Whenever we perform a scan (scanDevice Auto) that is fulfilled from the glass, the machine will beep until the panel is touched or the cover raised.

We're not explicitly making a call to make the tone and I can't find any configuration as to whether or not you want that operation to cause a beep (and it doesn't even seem to comply with the volume control on the device).
I don't see any options for turning off the beep on the device through the API for an operation (just for initiating beeps). Is there any way to disable this behavior?

2 - Interrupted scan jobs don't seem to be handled well.
If we have a preview dialog open and the user presses the home button, the scan job seems to be left in a bad state. On our device, just relaunching the WebBrowser app doesn't fix the state and we often have to reboot it.
Is there something that we can do to handle these types of scenarios?

3 - The capabilities reported by the device through (ricoh.dapi.data.ScannerCondition.. onCapability) doesn't match the same being reported by the emulator. I assumed that the main difference between the different models would be in the capabilities that each support.

Thanks,
Scott

Product ID:  1979711515

Vendor Name:  Plus Technologies

Application Type:  Web Application (Web BrowserNX)

Application Name:  My Print Delivery

URL Lovation:  https://sherlock/MyPrintDelivery/*

Target Version:  1.0

MFP Serial number: C768R210724

Is there some documentation on some of the advanced scan settings?

The C306 reports that it supports these things, that I didn't find in the documentation:
imageQuality, gamma, brightness, contrast, filter...

Brightness and contrast are pretty common, but I wasn't sure about the different gamma settings and the filters (mtf?)... and maybe any other settings that may be out there that I may want to account for.

I've searched the sdk docs for anything on these without any luck (wouldn't have known about them, if they weren't reported as supported by the C306.

Any documentation on this that you can provide would be appreciated (both on what the full domain of potential capabilities are and some info as to what the features do).

Thanks,
Scott

We are starting to develop the companion piece to our Authentication program.  This is a web based program that will be running in the Web BrowserNX and accessing the AAA compliant login provided by the custom auth.

I am having a little trouble getting started with this.  Can I schedule a few minutes with someone to help me find the javascript library necessary for this to work as well as the signing process for Web BrowserNX programs.

Thanks,

Keith Reinig

Plus Technologies

Hi,

I'm starting the process for filling out the PTEC test and noticed that in order for certification testing to allow for CAC software testing, we must first have tested in your lab with it.

How do I go about getting the CAC testing set up for our WebBrowserNX version?

Thank you!

-Sue Collins