When you're on a mobile supported device but viewing the desktop version there is a small link/banner letting you know the mobile site is available, so it's fairly easy to switch between the two.

CONF-26225 is part of what I mean in regards to macros on mobile.

Thanks John, we disabled it in the Beta and RC versions, we did not wish our user to visit this after upgrading and become confused. I might note that when you add fuller support to the mobile version and cookies have already been set to bypass to the desktop version, wouldn't you be shooting yourself in the foot? I would imagine almost every user will go to the full version due to no macro support.

How about support for us as macro authors who wish to provide mobile support? I have made a suggestion on CONF-26225 as to an implementation that would be fairly simple to implement for you guys and us to support as macro authors.

brett.ryan if you switch to the Desktop view from the Sidebar there's a cookie set to remember that (versus from the page banner which is a one time switch).

If you really want you can just disable the Mobile Plugin and users won't have the functionality.

There are several Macros that already render fine in Mobile view but we're are working on a fuller solution for Macros on mobile.

Are there any particular macros that you use more than others that you'd like to see Mobile support for?

Thanks for the update Sherif. We are anticipating the mobile support however my manager has requested the ability to disable it as it does not support editing and almost every page viewed renders without macros instructing the user to "click to full version".

We are wondering how we will go about supporting rendering macros on mobile versions.

Last tested with RC1 exhibited this behaviour.

Hi All,
The upcoming release of Confluence 4.3 (due out in a few weeks) has a dedicated mobile UI for Confluence.

This is mostly focused on view page, commenting and likes.

It does not support editing yet, this was deliberate as we wanted to focus on the primary use case for mobile - consuming pages and quick comments. We have raised another issue to support mobile editing for those interested: CONF-19523.

I'll mark this issue as resolved.

I second that commotion. We have users with videos (several formats) in their training pages. We're going to convince them that the SWF ones have to go

Is there any news on when video support will be included on iOS (iPAD)? We are evaluating using a Confluence WiKi for our Qquality Management System (ISO) and a fundamental requiremetns is that we would like to demostrate procedures using videos.

Great news, unfortunately we can't upgrade as most of our plugins aren't compatible. The adaptavist PLM bug has to be resolved before we can even think of upgrading.

It appears that the Confluence 4 editor works on iOS 5

Lack of commenting ability on iOS is a real problem. Being able to quickly give feedback on a blog post while on the move has been invaluable. Now we wait for iOS 5 – hopefully not for too long.

Thanks for the feedback, everyone.

The rich text editor is our biggest concern with full iPad support at the moment. We tried to implement a quick solution for commenting on iOS in Confluence 4, but had to drop it for this release. We're planning to have another go later in the 4.x cycle.

The upcoming release iOS 5 also brings some basic support for content-editable, which means that there might be a chance of using the full Confluence 4 editing experience in Mobile Safari without any additional effort on our part. We'll have to see what is there when the final iOS version ships, and what level of support is available in TinyMCE.

I'd like to suggest that Confluence support a different theme when viewed on a mobile browser like Safari on iPad. At the moment, Confluence works well on my iPad except that the pagetree on the LHS of the Documentation theme isn't rendered and therefore the main content if shifted to the left leaving a big gap on the RHS.

Even if this is a bug and gets fixed, I'd still like to be able to view using the easy reading theme on the iPad whilst still using the Documentation theme on my desktop.

Thanks Bill! Two finger scrolling works fine and I also learned something new about the iPad!

@michael_stone Perhaps you're referring to issue DOC-53 in the Documentation Theme? That issue is now resolved and will be bundled with Confluence 3.4? I believe two-finger scrolling also fixes the issue if you're not able to immediately upgrade.

Confluence on Safari on the iPad does not seem to support scrolling of pages that exceed the height of the screen. If my page is too long, it is cut off by the Confluence page footer and I can't see/access the rest of the page.

This makes Confluence pretty unusable on the iPad from my perspective, even from a content consumption perspective.

Is this the right issue for all Atlassian products having iPad support?

Just came from CRUC-3635 which focuses upon the Crucible aspect. Personally I find iPad use of Confluence and Jira workable so far. FishEye/Crucible are the unwieldy ones due to the many frames and unresponsive buttons – especially the "folder view minimise" button which means one is stuck with a small rectangle in the bottom right corner for viewing the code, diffs, etc.
If you indicate, I'll log as a separate issue.
Cheers for great products which our high-ratio-iPad-owning company will be purchasing at the end of our eval.
R.
p.s. greetings from the iPad.
p.p.s. Have you noticed there are some non-functional-req curios in this window? (e.g. the text entry performance is rather laggy in this window, the cursor moves oddly when the page is scrolled)? Log more issues?

I second Simon's comment, mind you I don't use the rich editor anyway. Wiki markup would be great.

I'd be more than happy to live with just Wiki markup...

Hi Simon,

Maybe there's something which the iPad just doesn't do...

Yes. iPad doesn't support contentEditable areas which TinyMCE requires.

See:

• http://tinymce.moxiecode.com/punbb/viewtopic.php?id=22165 and
• http://tinymce.moxiecode.com/punbb/viewtopic.php?id=22209

I'm a bit disappointed this is down as "Minor" in the priority. With the popularity of the iPad I would have expected it to be a little more important - to tell you the truth I was expecting it to be fixed in 3.3! Right now this is pretty major for us.

I'd love to know more about what the hold up is here. Maybe there's something which the iPad just doesn't do, if so it is worth saying because "Minor" just implies that Atlassian don't really view it as worth looking at.

I'm not going to beg... yet. But I wonder how many people have realised it doesn't work and just moved on without saying anything?

(as an aside, we took a few hours to make our web-based product work on the iPad, press released it, and it is currently our main source of inbound sales leads... there's a lot of energy there)

I just want to kick in my full support of this improvement! This would really, really help us a lot!

Hi All,
I'm going to split this into into 2 issues.

• Support for the iPad
• Support for Mobile Safari in the iPhone
  this will allow us to accurately track votes for each issue.
  I'll make this one the iPad issue as that seems to be most of your feedback above.

Would love to see this too because our company relies heavily on both confluence and the iPad. Apple needs to do their part too because you can't upload from the iPad.

I was hoping to use confluence and JIRA with the iPad when it's finally released here in Australia. Support coming soon? I'll give you beer!

I can only second that. The iPad is big enough to use the Confluence web interface. I use it in lieu of a notebook in meetings. Not being able to edit Confluence is a major nuisance.