-
Nice work so far, great improvement on the mobile theme. Fit's my 4.5' android screen well.
My little observation on using the mobile phone (with opera mini browser) in accessing wedge.org
* Works better this time, the width fits my 4.5' screen well. I believe it will do well in smaller screen.
* The ajax function not working on opera mini and when the page reloads, it doesn't work at all
Eg. If you click 'action' it will reload the page and do nothing. This bug is not in other browsers like default html android browser, ucweb or opera mobile.
-
Maybe this is not the right place but reading on my iPad 4 the name of the contributor and the title of the topic are on the Same line.
-
@Pentaxian that's the idea, yeah... My recent rewrite tried to restore as much of the desktop skin as I could, because it's simply better to retain all functionality, and just cut off any strings whose length isn't under our immediate control, like the topic titles...
@Wanchope, yup, it's the Wireless skin I've been using locally for some time, but I only uploaded it a couple of days ago here, because I felt it was ready for further testing by the audience... :)
I'm not 100% happy with font sizes, but at least now in Firefox and Android Stock, it's not as horrible as it used to be, phew...
The Ajax bug.... Never happened to me, really.
Then again, Opera Mini is NOT part of my mobile toolset, and I have no plans to change this: Opera Mobile is so much better, and even then, it's not as good as Chrome Mobile, so if you have an Android device, I'd simply recommend using Chrome, which is here to stay, unlike Opera Mini, because I really, really don't trust Opera for keeping Presto around, and worse, getting it up to date with today's standards, as they've already shifted all their efforts to Blink...
-
Maybe this is not the right place but reading on my iPad 4 the name of the contributor and the title of the topic are on the Same line.
It's the way it was programmed. Personally, I prefer something like this
topic title by {poster} on {date}. Avater Removed in Mobile theme! Cc @N
#suggestionThe Ajax bug.... Never happened to me, really.
Then again, Opera Mini is NOT part of my mobile toolset, and I have no plans to change this: Opera Mobile is so much better, and even then, it's not as good as Chrome Mobile, so if you have an Android device, I'd simply recommend using Chrome, which is here to stay, unlike Opera Mini, because I really, really don't trust Opera for keeping Presto around, and worse, getting it up to date with today's standards, as they've already shifted all their efforts to Blink...
I don't like opera mini too but chunk of my website users are accessing it with opera mini. Too sad :(
-
Opera Mini has a really good marketshare, its been a problem for my mobile theme too.
-
What matters, is that in a few years time, Opera Mini will be nowhere to be found.
As for having the title next to the user name -- what's the problem with that, exactly...? :huh:
-
What matters, is that in a few years time, Opera Mini will be nowhere to be found.
As for having the title next to the user name -- what's the problem with that, exactly...? :huh:
Not enough width, it will almost certainly get cropped by a good margin.
-
Not a problem but it can be confusing sometimes expecially if the poster have a long user name. Consider if my username is Android Operating System. The topic will look like ANDROID OPERATING SYSTEM - ON MOBILE THEME. I bet it will sound confusing.
-
Apparently I was not clear enough. The two texts are not only on the same line but also on the same place, I.e. the beginning of the line.
-
Apparently I was not clear enough. The two texts are not only on the same line but also on the same place, I.e. the beginning of the line.
A screenshot would be quite useful...... maybe? :ph34r:
-
(http://i216.photobucket.com/albums/cc264/Rubbd/image_zpsbe6e4755.jpg)
-
Just signaling: This problem is still there.
iPad 4/ Safari
-
Anyone else, too..?
-
No issues on my Nexus 4.
-
Well, anything Android is in the clear I suppose, since I do all my mobile dev on a Galaxy S3. But what about iOS?
-
Not sure if you are aware...the forum does not display well on the new Safari 7. Looks fine in FF 24 and Chrome 30.
-
Hmpf..! Stupid Safari... -_-
I did all I could to add support for it, and whatever it's supposed o support. I don't really know what's not working here. It seems to be related to the flexbox feature, but... I don't know, it's supposed to support it, isn't it..?
Can you, I don't know, emulate Safari 6 from within Safari 7?
PS: as a reminder-- as of now, none of the Apple browsers are available to ANYONE who doesn't pay them big money for one of their overexpensive, overrated machines. Considering I abandoned my iPod Touch 4 long ago, obviously I don't have iOS 7 on it (it's still on iOS 5.1, and my battery is depleted, and whatever), and can't test either.
So, I guess you're on your own to 'fix' it from their developer tools... (They DO have developer tools, don't they...?? No, at this point, I wouldn't be surprised if they wanted to screw everyone up.)
-
Yes, changing the user agent for Safari 6.1 does fix it. It really isn't that big of a deal as I can use Firefox or Chrome. Just thought I would mention it here since it is a new release.
Oh yeah, the front page of Wedge looks fine. It is only when you open forum threads that you see the issue.
-
What about now..?
Can anyone test on iOS 7, too?
-
Safari 7 on my iMac is still doing it.
I don't have an iOS device to check it with though and Safari 7 can only simulate iOS 6.1.
-
Very, very odd... It looks like it's still using display:flex, even after I uploaded a fix to disable it... :-/
-
Okay, I think I might have spotted the bug...
Technically, display:flex was turned into display:-webkit-flex for Safari 7+, but not "flex:1 0 auto" for instance; this is because I do the transforms in two different areas, and when I added Safari support, I forgot to also do it in the other area. (Given that I don't have access to one of these, no surprise here...)
I fixed that, please tell me if it works.
Also, for some reason, looks like the flexbox support variable doesn't work right now; I'll have to investigate further, as it's important for me to get it right.
-
Yes, it looks great now. Everything back to normal.
Also checked with the iPhone simulator running iOS 7.0.3 and it looks good there too.
-
Good to know!
Then, I'm keeping support for Safari 7 and iOS 7 when it comes to flexbox... ;)
Also, I've re-uploaded my latest changes.
Could you test again in both Desktop and Mobile Safari 7, and your Safari 6.1 simulation? Thanks..! This time, it should be good too, but I've also fixed the whole true/false thing, so that it will also work in Safari < 7.
-
Safari 6 & 7 in the desktop version looks good.
Safari 7 mobile version in the iPhone and iPad simulator looks ok except the user name is running into the title of the thread though I see that on a lot of sites when using a mobile device. Screen shot attached.
-
I'm still unable to figure out why the two overlap. They both use display: inline, and no floats, so they should remain in the flow.
Can you switch to the Weaving skin manually from your iOS simulator, and see if there are any similar problems in there..?
-
It looks good with Wuthering...
-
Hmm... Far from perfect, in fact: there's an unexplainable large empty area on the left of posts, and 'Nao' sticks right next to the status icons, when there should be a few pixels between them. Other than that, it looks good.
I've temporarily disabled flexbox on iOS 7. Can you guys test in both Weaving and Wireless..? Thanks.
-
On weaving the large blank space is gone now. On wireless the user name still runs into the thread title.
Sidenote using Safari 7 on Mac OS X 10.9: When attaching images, drag and drop only works for the first attachment. If you want to attach two or more you have to click the "Choose Files" button after the first attachment. Not that it is a problem though.
-
On weaving the large blank space is gone now.
And now, instead it's cutting off the userbox area.
Stupid Safari! I've always hated that browser... To think that you can't do without its engine on iOS. Safari, actually, is the #1 reason I went to Android. At least, that OS doesn't impose its own browser engine, and thus I can use Firefox to view Flash websites if I really need to, I can use Chrome to have hundreds of tabs, and I can use Opera if I'm nostalgic. (Not that much, really.)On wireless the user name still runs into the thread title.
Yeah... Very, very annoying. I'll have to find something else then. :(Sidenote using Safari 7 on Mac OS X 10.9: When attaching images, drag and drop only works for the first attachment. If you want to attach two or more you have to click the "Choose Files" button after the first attachment. Not that it is a problem though.
I only co-wrote that plugin (Dragooon started it, he did an excellent job), so I don't remember much about the process, but FWIW, since plugins are released separately, I can always fix that later. ;)
-
Overlap in a few spots. Screen shot attached.
-
Known issue. Already discussed on other topics. Please note that this is iOS only and as such, I can't test it myself and fix it. Someone else will have to figure it out. :-/
-
I've made a quick change to the template; can you re-test in Safari Mobile, and tell me if the problem is still there..?
PS: merged with the private topic. It didn't have any 'privatey' bits, so I didn't see why not.
-
The problem is still there!
-
Well, at least I can get rid of that ugly fix I made yesterday... :^^;:
I'm afraid it's due to the position: relative I have in the user name, then... Which means, it's pretty much impossible to fix it without rewriting the mini-menu layout system, and I'm, err... Not a fan of the idea. While getting the menu out of that particular DOM node (sorry for talking rubbish :P) would help with some earlier z-index issues (I already apologized!), it also means that any changes to the page dimensions would need to be passed on to the mini-menu manually, and... Well, it sucks.
-
What about now?
(In Wireless; not in Wilderless.)
-
Still there.
-
Oh, bugger...
Posted: November 9th, 2013, 11:33 AM
How 'bout now?
I insist, these tests must be done on Wireless, not Wilderless. Wilderless is the current 'default' mobile skin, so you have to consciously switch to it. If you didn't do it, then the previous test was for nothing.
If the current test works for you, then it means the profile mini-menus have to go from Wireless, at least in that position.
-
In Wireless: still there.
-
Hoping for this one to be the last... :^^;:
Changed Wireless to use floats instead. Seriously-- this one should work.
Changed Wilderless to use inline-blocks. I also tweaked the CSS to correctly align the elements vertically along the same line.
Please test both! Anyone who's got access to iOS, really.
-
Looks great to me. Just loaded it and all looks good!!!
-
On both skins? Which platform already?
-
Oops. I made a wrong manipulation on my Wireless file, and reverted it to the 'original'. I'm hoping the Wilderless works for both of you, and it's not just Wireless that worked, although I don't think it'd be too hard reproducing the float layout I'd made for it... :^^;:
Really, though, Wilderless is the way I'd like to fix it, including in Wireless, so hopefully it'll be the right one, eh..?
Hmm, one thing I'd like to try, though, is reverting Wilderless back to use display: inline instead of display: inline-block, so that I don't have to add a hack for it on older browsers, but then again... It's only for IE6 and IE7. I'm sure they've got a ridiculous user base, by now...
-
Both in Wireles as in Wilderless, still there. I feel for you!
-
Restored the float hack in Wireless; please test again. :^^;:
(Unfortunately it's not pixel-perfect, unlike the Wilderless hack...)
Can you remind me your version of iOS, already..?
Maybe it's a simulator-only bug, although I doubt it.
Posted: November 10th, 2013, 12:49 AM
Still waiting for feedback on this. :whistle:
-
I disagree it wasn't there when I checked it earlier... Was totally fixed. I am using ios7 with mobile safari. I will go check again right now as it WAS working.
-
Im thinking pentaxin is just looking at the pic I posted instead of the thread itself. Still looks fine to me.. Im going to see what I need to do to swap themes.
-
Yeah that could be the reason lol. I actually got fooled when using browserstacks (iOS 6 only) to generate a screenshot of this page. I only saw your shot. And thought it was broken.
Please test in both wireless and wilderless. It's important. Then I may do one final test later and we'll call it quits. ;)
-
Looks great on both themes.... The only thing I notice is the link tree gets a little smashed up at the end.. (runs out of space) but the iphone uses a smallish screen and I think most people know that and can deal with it. Otherwise it looks great. Display is very nice and no overlapping on either theme. Wireless or Wild---whatever how you spell it...
Once again iOS7 and mobile safari. Using an iPhone 4s.
-
Ok using an old iPad I have laying around. iOS 5.1.1 and mobile safari the issue is still there. Honestly being as ios 5.1.1 isn't supported by apple anymore I don't think I'd worry about it to much honestly. I think I have an iPod running iOS 6. I'll go check with that a sec.
-
Hey, my iPod is still running 5.1.1... :P Never bothered to upgrade, since I stopped using it a year ago (was getting too slow, really.)
I've found my cable, I'll just restart it, for old time's sake, and see if I can reproduce there, eh...
-
Holy cow... Wedge doesn't wanna load for me today.. Took forever.. Anyway..
iOS 5 and Ipad... Works great until logged in.. Once logged in the user name and reply number text overlap.
iOS 6 and iPod... Same as above
iOS 7 and iPhone.. Same as above
Seems to work perfectly until you are logged in. Then the overlap happens. Hope this helps some. I wasn't logged in before so my apologies. Once I saw the issue I re-checked with all the iOS stuff I have laying around.
-
iOS 5.1 + iPod Touch: works great in Wilderless, then as you imply, it fails once I log in. >_< Dunno why.
Yeah, still, that's a good direction to look into! At least I know that I can analyze both my ios CSS cached files, and see what the differences are.
Posted: November 10th, 2013, 06:51 PM
Does this happen on your posts only? (i.e. posts where you probably have a checkbox next to the post title...)
-
Well, got my answer... There was a JavaScript error, which occurred on all mobile themes, if the user wasn't logged in, and thus had no rights. (It wouldn't happen on boards where guests are allowed to post, but it doesn't matter.)
And as I expected, fixing this bug suddenly makes the CSS fail in guest mode as well. Meaning, well... That it's all due to a JavaScript problem in the first place, and CSS hacks won't help at all, eh.
Was looking in the wrong place... Now I need to determine what JS function changes anything in that area. My bet is on mini-menus, of course.
:edit: Confirmed. Disabling mini-menu code will make it work. Uh. So, it's back to being a CSS problem, I guess... :^^;: (As: CSS added by the JS function.)
-
Setting .mime to position: static, as I tried yesterday, makes it work on my iPod, but of course it screws up the menu. :-/
Seems to be the thing I dreaded. I'm not sure why it failed yesterday, though..??
-
Wireless and Wilderless both still overlap on iPad Air and iPad3 with ios7.
-
Yup... As I said, since I was able to reproduce on my iPod Touch with iOS 5.1, from now on I won't have to rely on others to tell me about whether it's okay or not.
Unfortunately, as I pointed out yesterday, I'm in a (sad) position where I have to consider disabling user menus entirely for iOS users.
-
Ahem.
Fixed.
Partially my fault.
Let's forget about it. I wasted enough time on that 'bug'.