Home

Website infinite scroll error

%3CLINGO-SUB%20id%3D%22lingo-sub-774932%22%20slang%3D%22en-US%22%3EWebsite%20infinite%20scroll%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-774932%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20error%20occurred%20while%20browsing%20this%20very%20forum%20using%20Edge%20Dev%2077.0.223.0%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20862px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F124599i5D131CC1068E5CAF%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Annotation%202019-07-26%20093514.png%22%20title%3D%22Annotation%202019-07-26%20093514.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-775471%22%20slang%3D%22en-US%22%3ERe%3A%20Website%20infinite%20scroll%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-775471%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F161329%22%20target%3D%22_blank%22%3E%40Tiago%20Freire%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHas%20the%20error%20happened%20multiple%20times%20for%20your%2C%20or%20only%20once%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3EFrank%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-775502%22%20slang%3D%22en-US%22%3ERe%3A%20Website%20infinite%20scroll%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-775502%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F352730%22%20target%3D%22_blank%22%3E%40V-FRROME%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BI%20got%20it%20this%20morning%2C%20too%2C%20about%207%20am%20CST.%26nbsp%3B%20I%20decided%20it%20was%20a%20fluke%20caused%20by%20a%20coding%20error%2C%20and%20didn't%20bother%20to%20report%20it.%26nbsp%3B%20I%20figured%20that%20Microsoft%20would%20catch%20it%20and%20fix%20it.%26nbsp%3B%20It%20seems%20to%20be%20fixed%20now%20at%201%20pm%20CST.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-775505%22%20slang%3D%22en-US%22%3ERe%3A%20Website%20infinite%20scroll%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-775505%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318339%22%20target%3D%22_blank%22%3E%40tomscharbach%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20appreciate%20the%20update.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3EFrank%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-776081%22%20slang%3D%22en-US%22%3ERe%3A%20Website%20infinite%20scroll%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-776081%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F352730%22%20target%3D%22_blank%22%3E%40V-FRROME%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F161329%22%20target%3D%22_blank%22%3E%40Tiago%20Freire%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrank%2C%20got%20the%20error%20this%20morning%20when%20I%20was%20scrolling%20down%20through%20the%20messages%2C%20using%20my%20mouse%20wheel.%26nbsp%3B%20The%20scrolling%20worked%20for%20eight%20%22Show%20More%20Conversations%22%20page%20refreshes%2C%20and%20then%20I%20got%20this%20on%20the%20ninth%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20833px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F124681iF47640E22321775E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Jibberish-1.jpg%22%20title%3D%22Jibberish-1.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnce%20the%20error%20happens%2C%20it%20goes%20on%20and%20on%20(I%20suspect%20that%20%22Website%20infinite%20scroll%20error%22%20is%20an%20accurate%20description)%2C%20so%20that%20each%20additional%20scroll%20down%20to%20%22Show%20More%20Conversations%22%20brings%20this%20result%2C%20seemingly%20endlessly%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20877px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F124683iAAFFAB734D62D61E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Jibberish-2.jpg%22%20title%3D%22Jibberish-2.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20did%20two%20things%20to%20test%20this%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%2C%20I%20opened%20the%20Discussion%20thread%20%22Decouple%20my%20feed%20from%20MSN%22%20to%20see%20if%20the%20thread%20was%20corrupted.%26nbsp%3B%20It%20does%20not%20appear%20to%20be%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20839px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F124684i15BFF83DAAC18F46%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Jibberish-3.jpg%22%20title%3D%22Jibberish-3.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESecond%2C%20I%20opened%20the%20Discussion%20site%20in%20Firefox%2C%20to%20see%20if%20the%20error%20was%20limited%20to%20Edge%20Chromium.%26nbsp%3B%20I%20got%20the%20same%20result%20with%20Firefox%20that%20I%20got%20with%20Edge%20Chromium%2C%20at%20exactly%20the%20same%20point%20(eight%20pages%20scrolled%20successfully%2C%20the%20ninth%20bombed).%26nbsp%3B%20So%20it%20isn't%20the%20browser.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20case%20of%20%22false%20expectations%22%2C%20or%20maybe%20rebellion%20at%20eating%20too%20much%20hash%3F%26nbsp%3B%20Got%20me%2C%20but%20have%20fun%20with%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-776136%22%20slang%3D%22en-US%22%3ERe%3A%20Website%20infinite%20scroll%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-776136%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F161329%22%20target%3D%22_blank%22%3E%40Tiago%20Freire%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F352730%22%20target%3D%22_blank%22%3E%40V-FRROME%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFollowing%20up.%26nbsp%3B%20%26nbsp%3BAs%20reported%20in%20an%20earlier%20comment%2C%20I%20got%20the%20%22infinite%20scroll%22%20error%20again%20this%20morning%20(5%20am%20CST)%2C%20at%20the%20ninth%20%22See%20More%20Conversations%22%20scroll-down%2C%26nbsp%3B%20using%20both%20Edge%20Chromium%20and%20Firefox%20browsers.%26nbsp%3B%20I%20just%20checked%20again%20(7%20am%20CST)%20and%20got%20the%20error%2C%20but%20this%20time%20at%20the%20eleventh%20scroll-down.%26nbsp%3B%20That%20suggests%20three%20things%3A%26nbsp%3B%20(1)%20the%20error%20is%20not%20message-thread%20related%3B%20and%20(2)%20the%20error%20behavior%20is%20somewhat%20idiosyncratic%2C%20but%20persistent%3B%20and%20(3)%20the%20error%20might%20be%20time%20dependent%20or%20server%20activity%20dependent.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20843px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F124693i781E01A7ACA3A817%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22jibberish-4.jpg%22%20title%3D%22jibberish-4.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20this%20point%2C%20I%20put%20the%20issue%20in%20your%20capable%20hands.%26nbsp%3B%20You%20should%20have%20no%20problem%20replicating%20the%20error.%26nbsp%3B%20I'm%20taking%20my%20hands%20off.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-776499%22%20slang%3D%22en-US%22%3ERe%3A%20Website%20infinite%20scroll%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-776499%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F352730%22%20target%3D%22_blank%22%3E%40V-FRROME%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20did%20a%20quick%20check%20this%20morning%20(July%2028)%2C%20and%20replicated%20the%20error%20on%20each%20of%20the%20following%20permutations%2C%20getting%20identical%20results%20on%20each%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(1)%20W10%20Pro%2C%20both%20Edge%20Chromium%20Dev%20Version%2077.0.223.0%20and%20Firefox%20Quantum%2068.0.1%3CBR%20%2F%3E(2)%20W10%20Home%2C%20both%20Edge%20Chromium%20Dev%20Version%2077.0.223.0%20and%20Firefox%20Quantum%2068.0.1%3CBR%20%2F%3E(3)%20Solus%20OS%204%2C%20Firefox%20Quantum%2068.0%3CBR%20%2F%3E(4)%20W8%20Pro%2C%20IE%2011%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20%22%3CEM%3EFor%20%22.%22%20left-hand%20operand%3A%20Expected%20a%20hash%2C%20but%20this%20has%20evaluated%20to%20a%20string%3C%2FEM%3E%22%20error%20message%20isn't%20widely%20reported%2C%20but%20it%20is%20common%20enough%20to%20suggest%20a%20Java%20API%20Freemarker%20coding%20error%20related%20to%20a%20counter.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Tiago Freire
Occasional Contributor

This error occurred while browsing this very forum using Edge Dev 77.0.223.0

 

Annotation 2019-07-26 093514.png

6 Replies

@Tiago Freire 

 

Has the error happened multiple times for your, or only once?

 

Thanks,

Frank

@V-FRROME   I got it this morning, too, about 7 am CST.  I decided it was a fluke caused by a coding error, and didn't bother to report it.  I figured that Microsoft would catch it and fix it.  It seems to be fixed now at 1 pm CST.

@tomscharbach 

 

I appreciate the update.

 

Thanks,

Frank

@V-FRROME  @Tiago Freire 

 

Frank, got the error this morning when I was scrolling down through the messages, using my mouse wheel.  The scrolling worked for eight "Show More Conversations" page refreshes, and then I got this on the ninth:

 

Jibberish-1.jpg

 

Once the error happens, it goes on and on (I suspect that "Website infinite scroll error" is an accurate description), so that each additional scroll down to "Show More Conversations" brings this result, seemingly endlessly:

 

Jibberish-2.jpg

 

I did two things to test this error.

 

First, I opened the Discussion thread "Decouple my feed from MSN" to see if the thread was corrupted.  It does not appear to be:

 

Jibberish-3.jpg

 

Second, I opened the Discussion site in Firefox, to see if the error was limited to Edge Chromium.  I got the same result with Firefox that I got with Edge Chromium, at exactly the same point (eight pages scrolled successfully, the ninth bombed).  So it isn't the browser.

 

A case of "false expectations", or maybe rebellion at eating too much hash?  Got me, but have fun with it.

 

 

@Tiago Freire @V-FRROME 

 

Following up.   As reported in an earlier comment, I got the "infinite scroll" error again this morning (5 am CST), at the ninth "See More Conversations" scroll-down,  using both Edge Chromium and Firefox browsers.  I just checked again (7 am CST) and got the error, but this time at the eleventh scroll-down.  That suggests three things:  (1) the error is not message-thread related; and (2) the error behavior is somewhat idiosyncratic, but persistent; and (3) the error might be time dependent or server activity dependent.

 

jibberish-4.jpg

 

At this point, I put the issue in your capable hands.  You should have no problem replicating the error.  I'm taking my hands off.

 

@V-FRROME 

 

I did a quick check this morning (July 28), and replicated the error on each of the following permutations, getting identical results on each:

 

(1) W10 Pro, both Edge Chromium Dev Version 77.0.223.0 and Firefox Quantum 68.0.1
(2) W10 Home, both Edge Chromium Dev Version 77.0.223.0 and Firefox Quantum 68.0.1
(3) Solus OS 4, Firefox Quantum 68.0
(4) W8 Pro, IE 11

 

The "For "." left-hand operand: Expected a hash, but this has evaluated to a string" error message isn't widely reported, but it is common enough to suggest a Java API Freemarker coding error related to a counter.

Related Conversations
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
2 Replies
Early preview of Microsoft Edge group policies
Sean Lyndersay in Discussions on
65 Replies
*Updated 9/3* Syncing in Microsoft Edge Preview Channels
Elliot Kirk in Articles on
203 Replies