https://avo.cool logo
I'm running into an issue with Windows? and Edg...
# avo-2
m
Thread automatically created by rickychilcott in #740893011994738751
s
They are on Windows 11 and tried on both Edge and Firefox.
I should also say "it works on my machine" locally and in production. I'm on Mac OS X with Chrome/Brave
l
Hey @strong-restaurant-36788 I'll try to reproduce it at verify If it's a problem only on windows. I usually use Firefox on Linux and it works fine
l
looks like a JS error to me
I need to find a windows machine...
s
That’s what I thought. But the dev console wasn’t giving any hints.
l
I was able to reproduce it, it happens on new page, edit works as expected
s
Cool. This is one of those non-database backed resources. So thee is no edit for us to try but I’m glad the issue just isn’t on our machine.
l
Thanks for reporting it
@strong-restaurant-36788 let me know when you have 5 minutes to test something. I think i figured out the issue
Probably
Partner.default.accepted_memberships.map(&:user).map { |u| {label: u.decorate.name_and_email, value: u.id} }
include nil values, try to add an
.compact
to it and let me know if still verifying this issue
s
The output of that (without compacting) is:
Copy code
ruby
[{:label=>"Ricky Chilcott (ricky@somewhere.com)", :value=>4},
 {:label=>"Eric Ryan (eric@somewhere.com)", :value=>10},
 {:label=>"Megan Drapcho (megan.drapcho@somewhere.com)", :value=>882},
 {:label=>"Paul Lamb (paul.lamb@somewhere.com)", :value=>1351},
 {:label=>"Erin Sykes (erin.sykes@somewhere.com)", :value=>4182}]
Is it possible the parens are doing something? I can try (by redeploying) and then asking a team member to try it out in about an hour.
l
no hurry, if still verifying the issue check the dev console for any JS errors
s
parens / @ isn't the reason. Same with:
Copy code
ruby
[{:label=>"Ricky Chilcott", :value=>4},
 {:label=>"Eric Ryan", :value=>10},
 {:label=>"Megan Drapcho", :value=>882},
 {:label=>"Paul Lamb", :value=>1351},
 {:label=>"Erin Sykes", :value=>4182}]
l
hmm and none console error?
s
I'm going to have to chalk this up to 🤷‍♂️. After rolling everything back to my previous code, everything is working now? I don't know if this team member had a subtle browser update or if there were other things affecting it, but it seems ok now. Sorry for the noise.
l
Sure, no worries, glad that it's everything working as expected now!