| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Developing a userform for the hunting tool, signs in background, loads the default profile page, zooms-out to 70 percent to fit all the project options in the view. When making a change to the project selection, a script error pops up on ticking or unticking a box (screenshot). The boxes tick/untick before the error appears and when saying yes or no, does not reappear until changing additional selections. When saving and recalling the profile page, the boxes changed show as properly stored.
This runs in Office 2016/365, utilizing webbrowser1 calls in a form frame, which provides an in-spreadsheet web browser. Is this the office version of IE doing this (?), where it seems it's using the regular OS IE web engine of Windows 10 (v11 I think). When loading IE11 separately and going to sign-in it shows to have remembered user/password, but inside office it does not, so the script takes care of signing in, short for, it could be a different IE, 7 is suggested. Emulating a particular version is discussed here https://weblog.west-wind.com/posts/2011/may/2...specifying-the-ie-version, revision August 2016, but that is getting over my head at this time... think this whacks which ie is used by W10. "But there's a snag: The Web Browser Control is - by default - perpetually stuck in IE 7 rendering mode. Even though we're now up to IE 11 and a reasonably HTML5 compatible browser, the Web Browser Control always uses the IE 7 rendering engine by default." It's not a drama, clicking yes or no to get past, but change all projects is potentially 7 pop-ups, an annoyance for sure to those who do frequent profile editing. thx Edit: OK, scrap all that as .WebBrowser1.Silent = True puts the pop-up errors out of commission, though a programmer at the Expert Exchange wrote it would not. Changes are saved properly when applying. The internal error is though all yours ![]() |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
'In-Office 365' browsing on Windows 10 of the WCG site does reveal a few pieces that don't appear all too dandy... the 'silent' setting just suppresses all errors now (sign-in proved the hardest to get around the wayward pines... was needing multiple ReadyState tests before the injection of credentials could go ahead.)
Do While .WebBrowser1.Busy: DoEvents: Loop Do While .WebBrowser1.ReadyState = False: DoEvents: Loop The fun bit is, even while browsing and reading the forums being signed-out, the profile buttons give near instant access, opening all sorts of avenues... me custom WCG browser. :O) (Buttons look clunky, but fit for purpose was the first goal) ![]() |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
Sekerob,
----------------------------------------Only 8.3% of users visiting our website over the past month use Internet Explorer. Of those, 93.4% use IE 11. That means that less than 0.5% of users visiting the website use some form of IE before IE 11. That number is constantly going down. As a result, we do not test with nor do we fix issues related to bugs found in IE 7/8/9/10. The standards have changed since those versions and we simply cannot take the time to be backward compatible with such a small and diminishing portion of the user population. Can you go to this page: https://www.whatismybrowser.com/ and tell me what browser it reports? [edit] added missing 'cannot' [Edit 1 times, last edit by knreed at Oct 11, 2016 10:10:57 PM] |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Ran the test right during my previous post and as per the lit, IE7 engine is default used by Office 365/2016, which I presume has to do with corporate backward compatibility issues for the old apps they've got surely running. As for "we simply take the time to be backward compatible with such a small and diminishing portion of the user population.", surely there's a 'not' word missing in that sentence
. It's unimportant, the point is to get at the data, and 4 avenues basically led to below code needed which essentially strips each and every piece of froth and leaves the naked text, which allows to find the target info, in the case of e.g. locating the various account keys./codesIf Importformat = "text" Then Late declaration, then If Importformat = "text" Then Range("A1").PasteSpecial xlPasteAll to get the whole page as the form inside the page focuses the Copy-All on just the member name, and that's the last interested in once signed in. Crude, but it works 100% repeatable. |
||
|
|
|