Marvel Studios
Welcome to MarvelStudios, a community for discussing all things related to Marvel TV/Film productions with a focus on Marvel Studios!
We want this to be a place for members to feel safe to discuss and share everything they love about Marvel Studios productions. Please feel free to take part and help our community grow!
Upcoming TV/Film:
- Kraven The Hunter - Dec 13, 2024 (Non-MCU)
- What If...? - Season 3 - Dec 22, 2024
- Your Friendly Neighborhood Spider-Man - Season 1 - Jan 29, 2025
- Captain America: Brave New World - Feb 14, 2025
- Daredevil: Born Again - Season 1 - Mar 4, 2025
- Thunderbolts* - May 2, 2025
- Ironheart - Season 1 - Jun 24, 2025
- The Fantastic Four: First Steps - Jul 25, 2025
- Eyes of Wakanda - Season 1 - Aug 6, 2025
- Marvel Zombies - Season 1 - Oct 2025
- Wonder Man - Dec 2025
MCU TV/Film Discussion:
- Agatha All Along (Sep 2024)
- Deadpool & Wolverine (Jul 2024)
- X-Men '97 - Season 1 (Mar 2024)
- Echo - Season 1 (Jan 2024)
- What If.... - Season 2 (Dec 2023)
- The Marvels (Nov 2023)
- Loki - Season 2 (Oct 2023)
- Secret Invasion - Season 1 (Jun 2023)
Non-MCU Discussion:
- Venom: The Last Dance (Oct 2024)
- Madame Web (Feb 2024)
Misc Discussion:
- D23 2024 Discussion (Aug 2024)
Related Communities:
While posting and commenting in this community, you must abide by the Lemmy.World Terms of Service: https://legal.lemmy.world/tos/
-
Posts or comments that are homophobic, transphobic, racist, sexist, ableist, or advocating violence will be removed.
-
Be civil: disagreements happen, but that doesn’t provide the right to personally insult others.
-
Spam, self promotion, trolling, and bots are not allowed
-
Shitposts and memes are allowed until they prove to be a problem.
Regarding spoilers; Please put "(Spoilers)" in the title of your post if you anticipate spoilers, as we do not currently have a spoiler tag available. If your post contains an image that could be considered a spoiler, please mark the thread as NSFW so the image gets blurred. As far as how long to wait until the post is no longer a spoiler, please just use your best judgement. Everyone has a different idea on this, so we don't want to make any hard limits.
Please use spoiler tags whenever commenting a spoiler in a non-spoiler thread. Most of the Lemmy clients don't support this but we want to get into the habit as clients will be supporting in the future.
Failure to follow these guidelines will result in your post/comment being removed and/or more severe actions. All posts and comments will be reviewed on a case-by-case basis. This means that some content that violates the rules may be allowed, while other content that does not violate the rules may be removed. The moderators retain the right to remove any content and ban users. We ask that the users report any comment or post that violates the rules, and to use critical thinking when reading, posting or commenting.
view the rest of the comments
Feels weird to me that the & error still exists. Who do we have to blame for this, Google?
It is not an error. It is an html code (for ampersand, all codes start with &, in this case amp means ampersand) that for some technical reason that is beyond me gets wrongly parsed into text.
So it's not an error it's just that the applications are coded such that sometimes it incorrectly displays it in a way that it shouldn't, got it.
It's a Lemmy v.18 issue, so instances like Lemmy.world that haven't updated yet still see it happen.
Well, it's not just a Lemmy issue at all, though. It's on a bunch of websites across all the browsers I've ever used. It's kind of neat if it weren't so dumb that it's persisted for so long.
What do you mean?
The & error occurs when somebody types "&" but it shows up as & in messages or titles due to some sort of problem with parsing or sanitizing the text input, idk the specifics. In order to even show this on lemmy.today I had to type that amp; part in manually a second time because it automatically changed to "&" otherwise. It's been around for more than a decade already.
Lol. I don't think what you're describing is an issue for all clients. I'm using Sync and all I'm seeing is ampersands displayed correctly.
Ah, for reference then:
Does this in Liftoff as well. Always takes me a moment to remember what's happening in the titles.
The what error?
The amp; error that follows after ampersands.
I don't see it in Sync it seems.