Hey everyone,
Happy to share the first beta of Blocs for Mac 6.3 
This exciting new version is packed with 30 new features to explore and test, some of them shown off last week here.
Happy testing 
6 Likes
Just bumping this thread, donāt forget to test and file bugs if you encounter any 
2 Likes
Hey Norm,
Been testing the WordPress features specifically, created a few (mostly layoutless) themes (so purely testing functionality), but so far the Secondary menu has been working great.
Could you by any means clarify the following from the beta notes?
ā¢ Added WordPress styling to active marker on WordPress Loop Columns.
This I havenāt tested yet, but not sure what you meant with the āactive markerā.
Of course 
Before it was hard to tell if a column was being used as part of a WordPress loop when it was selected.
In Blocs 6.3 itās a lot clearer now as the selection marker is purple and it has a little WordPress logo in the top right corner. Just a little UX touch
2 Likes
Ah I see. I was testing with a simple āWP contentā bric on the home page, hence I missed that. Great addition though. Will test this too 
1 Like
Love it! Small but helpful feature, thx @Norm
2 Likes
@Norm Just had a chance to test out the find and replace feature and it worked great and found text as well as items I was looking for in code blocks. Woohoo and fabulous job! You just saved me so much time. 
Note that I didnāt actually use the replace feature as Iām one to manually update the text if needed (been burned by too many funky/flakey implementations in other apps).
Also one nit, and it could simply be my own project implementation as I have several code blocks that had HTML within. I noticed that going forward in search, it would take me through one of the code blocks, move out to more normal content where Iād replace things and at some point Iād return back to the code block again without looping back to the beginning. Going backwards in find was much more consistent, but like I said, it could have simply been the layout of my project thatās funky, but I figured itās worth a mention so that you can keep an eye out for this.
I know many others are excited for many of the other features/improvements, but for me Iām now calling this the āFind and Replaceā release. 
2 Likes
@Norm Did another search tonight and found a bug. It doesnāt look like search is looking in the Alt fields for images.
Itās not a bug, find and replace only searches textual content on the page. It doesnāt find data attributes and any matches in the actual code.
This makes sense except that alt text is textual content. Although not always used by sighted folks, alt text is very often used and can be the only content for folks who are blind or have low vision. So at least for me, I treat this as any other kind of text, just applied in a different spot.
Why do I care and how does this interact with my workflow? One of my third party tools does spellchecking and there was a word I typoād that happened to be in an alt tag. Doing a search and replace didnāt work.
Totally understand, itās just not supported in find and replace within Blocs as itās not visible on the design canvas. Find and replaces works like find and replace in Pages, right now itās just the visual text that is highlighted and scanned.
Iāll see if I can expand support for the underlying data attributes in the future.
1 Like
Okay no worries. As thereās various intricacies here, maybe you can add a note to the docs within Search/Replace that speaks to whatās included/excluded to steer folks in the right direction?
Regardless, Iām still very much thrilled with the new Search and Replace as this is a huge improvement over what we previously had. 
1 Like