Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

The html tag <object> behaves differently when communicating over Wi-Fi or LTE. For WLAN, the behavior is as expected and for LTE a new session is always called

  • 1 件の返信
  • 1 人がこの問題に困っています
  • 3 回表示
  • 最後の返信者: Frank_VGV

more options

Hello, the html tag <object> behaves differently when communicating over Wi-Fi or LTE. For WLAN, the behavior is as expected and for LTE a new session is always called after logging in, because the transferred SessionID is not returned. Cookies are turned on in both cases. We have some websites (Example www.vw-baev.de/Registrierung) and a small portal, which we show / integrate in this website by tag <object>. We use now tag <iframe> and we succeed, but why does LTE not work? The small portal was developed with MS Visual Studio 2015 and ASPX. Many Thanks Frank

Hello, the html tag <object> behaves differently when communicating over Wi-Fi or LTE. For WLAN, the behavior is as expected and for LTE a new session is always called after logging in, because the transferred SessionID is not returned. Cookies are turned on in both cases. We have some websites (Example www.vw-baev.de/Registrierung) and a small portal, which we show / integrate in this website by tag <object>. We use now tag <iframe> and we succeed, but why does LTE not work? The small portal was developed with MS Visual Studio 2015 and ASPX. Many Thanks Frank

すべての返信 (1)

more options

Sorry, the tags are not displayed correctly. We switched from "<" object ">" to "<" iframe ">".