Discourse에서 iOS 26의 고정 위치 요소 버그

[awesomerobot (Kris)]

업데이트: iOS 26.1 릴리스와 함께 Apple은 이 주제에서 논의된 가장 중요한 버그들을 해결했습니다. 귀하 또는 회원분들이 iOS에서 Discourse의 레이아웃 문제를 겪고 있다면, 해당 기기가 26.1 이상으로 업데이트되어 있는지 반드시 확인하세요.

iOS 26가 공식적으로 출시되었지만, 일부 Safari 문제가 해결될 때까지 업데이트를 보류하는 것을 권장합니다. 이는 iPhone과 iPad에서 온스크린 키보드를 열면 고정 위치 요소가 제자리에 있지 않게 만드는 시각적 문제입니다. Discourse의 경우 헤더, 모바일 푸터, 작성기(composer), 채팅이 이에 해당합니다.

이 버그를 면밀히 주시하고 있으며, 그 동안 일부 우회 방법을 구현하는 데 노력하고 있지만, 문제가 Safari의 창 높이 계산 방식(웹사이트가 직접 제어할 수 없는 부분)과 관련되어 있기 때문에 해결책은 상당히 제한적입니다.

이러한 문제는 고정 요소와 입력 필드를 가진 모든 웹사이트에 영향을 미치는 것으로 보입니다.

더 자세한 정보가 궁금하시다면, webkit 팀에 제출된 버그 보고서를 여기서 확인하실 수 있습니다:

297779 – [ios26 Beta 7] Fixed elements move up and down when the scroll...

Apple 개발자 포럼과 Stackoverflow에서도 추가적인 세부 사항과 보고서를 찾을 수 있습니다.

이러한 문제가 해결될 시점을 예측하기는 어렵지만, 더 많은 정보가 밝혀질 때마다 이 주제를 업데이트하겠습니다.

상태 업데이트:

2025-09-17T04:00:00Z — Apple은 이 버그를 해결로 표시했으며, 이제 출시 과정을 거치면 될 것으로 보입니다.

2022-09-25T04:00:00Z — Apple은 iOS 26.1 (23B5044I) 베타 버전에 수정 사항을 포함했습니다.

2025-11-03T05:00:00Z — 고정 요소 위치 문제를 해결하는 iOS 26.1이 출시되었습니다… iPad에서 여전히 작성기(composer) 문제가 있을 수 있다는 보고가 있습니다.

2025-11-10T05:00:00Z — 일부 진전이 있었지만, 이 문제가 완전히 해결되지 않았다는 보고가 계속되고 있습니다: iOS 26 bugs still persist on 26.1

[Radio_TVGuy (SCA and SWM have both merged.)]

Yeah I’ve noticed this when trying to type a response or a new post on my iPhone. It’s been getting really annoying. I mainly use my PC now for Discourse forums as a result.

I have iOS 26 installed and have been using the Public Betas. It’s wonderful, but trying to respond to a new post or existing reply in Discourse can get a bit mucky. Will wait until a fix comes out.

[DudeMeister]

You’ll update as you learn more?

The iOS26 Beta has been running for 4 months with exactly this issue. How could this sneak up on you?

[asa]

That’s not quite accurate. The problem only started with iOS Beta 7. That doesn’t make it any better, but I hope for a quick fix.

[awesomerobot (Kris)]

There are often problems with betas that are resolved by the time the public release happens, and issues change even between beta versions. In this case it’s a very basic browser height calculation that’s broken and avoiding the problem is not at all trivial.

I don’t think it’s odd for us to put the onus on Apple to fix this, it’s a very sloppy issue that will impact thousands of sites beyond Discourse, and even occurs in Apple’s own support forums.

[DudeMeister]

I think the link is tagged with Beta 7 because that’s when it was reported. I had the dev beta installed from day 1 in June and experienced the issue from the start.

It seems like it will be fixed in the next developer beta, according to the linked thread. Still, communication about this from Discourse was neither proactive nor precise.

[DudeMeister]

Then the story goes you monitored this for Beta 1-9, held out hope it’s going to be fixed with the final release and then quickly tell people to not update (like they won’t) once it’s been pushed to the general public without the fix?

I get that addressing the problem is out of your hands but one would expect more attention to a show stopping problem on the most important platform.

[NateDhaliwal]

@DudeMeister

I had the dev beta installed from day 1 in June and experienced the issue from the start.

Did you report it anywhere here that you experienced these problems?

[awesomerobot (Kris)]

@DudeMeister

quickly tell people to not update (like they won’t)

I understand you’re upset about the bug, but you’re criticizing us for not notifying everyone about an issue in beta releases while also telling us the notification wouldn’t stop anyone from updating anyway… so it seems you’re holding us conditions that are impossible to satisfy.

In more positive news, someone from Apple’s side has responded to the report on their bug tracker, and it sounds like they already have a fix and it just needs to make its way through their software release process. 297779 – [ios26 Beta 7] Fixed elements move up and down when the scroll direction changes

[DudeMeister]

I was only made aware of this platform by this announcement. I had raised the issue in my community before realizing it’s not being addressed.

@awesomerobot You are responding to something I didn’t say. I was trying to figure out how your testing of the beta went to have led to this announcement. I suppose I don’t want to believe that you only became aware of the problem when the public update was pushed.

Glad to hear it is getting addressed. Ironically in a dev beta first. Might be time that someone in the team gets their device on them.

[tvavrda (Tomas Vavrda)]

@DudeMeister

how your testing of the beta went to have led to this announcement

I am quite happy with how it went. It is not on Discourse to test on Apple’s behalf. If there is a webkit bug in iOS beta, I would expect it to be solved in production. I don’t want to be even informed about it here on meta. There might be hundreds of such bugs. Of course, it’s iOS beta. They should be all gone by the time it gets released. And if not – we will be notified here. It’s perfect.

[sok777 (sok)]

unfortunately I’m on RC (Release Candidate) which is typically the final release, and it still there.

Very annoying, but I’m not sure why some users are pointing the finger at the team here. It’s a WebKit bug with no workaround.

[sok777 (sok)]

Sorry, just to clarify - this was released on Monday 15th. 26.0.0.

Last year, 18.0.1 was released 2.5 weeks after the first roll-out. By this timeline, we can expect 26.0.01 within about 14 days.

[rivohor]

How do you fix this?

[Jagster (Jakke Flemming)]

By waiting next bug fix from Apple?

[sok777 (sok)]

Quick update:

I just updated to 23A341 (different from the RC build - 23A340) and the bug is still there.

I think we’ll have to wait for 26.0.1 which may come out in 7-10 days.

[Octoberon]

Can confirm. I’ve just tried again with the latest beta and the bug remains.

[pmusaraj (Penar Musaraj)]

Hooray, today’s beta, iOS 26.1 (23B5044I), seems to fix the positioning issues.

[TFF_SD]

@NateDhaliwal

Did you report it anywhere that you were having these issues?

I reported the issue to Apple since Beta 4 (and all subsequent versions). It was useless.