Closed damianmgarcia closed 3 months ago
Hi Damian, this is Matej from the Chrome Web Store review. Thank you for your reply and for looking into it.
I am sending a screenshot and links. If there is something else I could do, let me know. I would be happy to help. I believe every blocked company is affected.
Darwin Recruitment https://www.linkedin.com/jobs/search/?currentJobId=3994565303&geoId=106693272&keywords=Darwin%20Recruitment&origin=JOB_SEARCH_PAGE_KEYWORD_AUTOCOMPLETE&refresh=true
Edit: added links and more examples Edit2: I have been able to replicate this issue on my second account and also on freshly created third account through VPN in different country and all details different. However when I log out and use no account your Extension works normally.
Wonderful, this is excellent! It looks like they are doing A/B testing. I can see from your screenshots that LinkedIn slightly changed the layout, where the company name and location are separated by a middle dot, as you pointed out earlier.
I would like to update the extension so that it can detect this new layout, and would appreciate some more of your help, if you don't mind. :)
Basically, it would be helpful if I could see the HTML code of the job listings so that I can see what LinkedIn changed. I made a short 1-minute video that shows how to capture the job listings code: https://drive.google.com/file/d/1A5BND6l5ozEim4C7uByXZ8n0x58Z0zEk/view?usp=sharing
If you're able to get a copy of the code that holds the job listings by following along with the video, you can paste the code in a TXT file, save it, and then email it to me (damian at outlook dot com), or you can share it via your preferred cloud storage service, like Google Docs, etc.
The steps in the video are:
Thank you so much for your help! :)
This issue is resolved in version 5.0.1, which has been sent to Chrome Web Store, etc., for review. The review process usually takes 1-3 days. I'll update this thread once the new version has been published to the Chrome Web Store.
Thanks so much for bringing this issue to my attention and for all of your help @Matej9937! Your support was critical in resolving this issue!
The below is a bug report by Matej from their Chrome Web Store review. Thanks Matej!